~jole

i write code

~jole/public-inbox

Last active 3 years ago
View more

Recent activity

Re: Email-based workflow questions 3 years ago

From Jonas to ~sircmpwn/sr.ht-discuss

On Thu Jul 15, 2021 at 12:28 AM CEST, Eli Schwartz wrote:
> Could you share with us, the error you got? An example project + patch
> which didn't work?
I got the error message "empty ident name (for <>) not allowed", but
after using curl like Chris suggested worked, i toyed around and
eventually solved it by using pipe -m. It seems without -m it strips the
metadata and so git doesn't know who to attribute the commit to?

> git format-patch is internally used by git send-email to create the
> actual mail message. It's definitely a bug *somewhere* if an attached
> patch will apply, but an inline patch won't. (That bug may be in the
> tools, or your process, or the mail system... but the bottom line is it
> is certainly supposed to work, so something has gone wrong.)
It would seem aerc, or more accuartely me misusing it, was at fault. The

Email-based workflow questions 3 years ago

From Jonas to ~sircmpwn/sr.ht-discuss

Hi list
I am playing around and getting used to email based collaboration, but i
notched something strange.

I can send patches with `git send-email`, and these are recongized by
sourcehut's web interface. However I am unable to apply these with `git
am` like
https://man.sr.ht/git.sr.ht/send-email.md
recommends. `git apply` does work but this is only applied to the
working tree, and not as a commit.

I figured `git format-patch` is what I needed and this does work and the
patches are applied as commits when i use `:pipe git am -s` in aerc.
However, when attached it seems sourcehut doesn't preview patches in the web

Re: [PATCH v3] add another md test file 3 years ago

From Jonas to ~jole/public-inbox

On Wed Jul 14, 2021 at 10:42 PM CEST, Jonas wrote:
> maybe this time!

> commit a94f6bf7ebba673c5184e4136c8018c230f537e2 (HEAD -> master)
> Author: Jonas Elvedal Hole <jonas@jole.xyz>
> Date:   Wed Jul 14 22:27:20 2021 +0200
> 
>     add test2.md
> 
>         Signed-off-by: Jonas Elvedal Hole <jonas@jole.xyz>


Thanks! Only like 4 tries :-P

[PATCH v3] add another md test file 3 years ago

From Jonas to ~jole/public-inbox

maybe this time!

[PATCH v2] add another md test file 3 years ago

From Jonas Elvedal Hole to ~jole/public-inbox

---
this is joel again! i really hope this works

 test2.md | 46 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 46 insertions(+)
 create mode 100644 test2.md

diff --git a/test2.md b/test2.md
new file mode 100644
index 0000000..b78c77d
--- /dev/null
+++ b/test2.md
@@ -0,0 +1,46 @@
# normal
[message trimmed]

Re: [PATCH] add another md test file 3 years ago

From Jonas to ~jole/public-inbox

---
i hope this works
- joel

test2.md | 46 ++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 46 insertions(+)
create mode 100644 test2.md

diff --git a/test2.md b/test2.md
new file mode 100644
index 0000000..b78c77d
--- /dev/null
+++ b/test2.md
@@ -0,0 +1,46 @@
[message trimmed]

Re: [PATCH] add another md test file 3 years ago

From Jonas to ~jole/public-inbox

On Wed Jul 14, 2021 at 10:00 PM CEST, Jonas Elvedal Hole wrote:
> hi jole, i figured you'd want some more test coverage!
>
> - joel

You must be new to using git with email. Comments must be written
between the two --- as that is ignored by git am.

[PATCH] add another md test file 3 years ago

From Jonas Elvedal Hole to ~jole/public-inbox

hi jole, i figured you'd want some more test coverage!

- joel

---
 test2.md | 46 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 46 insertions(+)
 create mode 100644 test2.md

diff --git a/test2.md b/test2.md
new file mode 100644
index 0000000..b78c77d
--- /dev/null
+++ b/test2.md
[message trimmed]

Re: Switching folders directly 3 years ago

From Jonas to ~sircmpwn/aerc

> Yes, using :cf.
Perfect!

Switching folders directly 3 years ago

From Jonas to ~sircmpwn/aerc

Hi
I can use :next-folder and :prev-folder to switch folders, but can i easily jump to a specific one by name? Thanks.