Hi all,
I noticed that when I use aerc to apply a patchset using the command
:pipe git am
The produced git commit message is missing the mail subject that
contains the first commit line. It happens even if I use the `-k`
flag.
The problem doesn't happens if I curl the patch mbox and apply it
manually (also using `git am`.
Is there something that I am doing wrong or this is an issue with
aerc itself?
Cheers.
Oscar
Hi there,
On Sun Apr 9, 2023 at 4:21 PM CEST, 'Oscar Campos' wrote:
> I noticed that when I use aerc to apply a patchset using the command>> :pipe git am
Consider using it with -3 by default. git can be rather picky otherwise,
> The produced git commit message is missing the mail subject that> contains the first commit line. It happens even if I use the `-k`> flag.
Not sure what the -k is supposed to do. You'd want -m or pipe it from the
message list, then it includes the headers.
--
Moritz Poldrack
https://moritz.sh
On Sun Apr 9, 2023 at 3:51 PM IST, Moritz Poldrack wrote:
> Consider using it with -3 by default. git can be rather picky otherwise,
Thanks for the tip
> Not sure what the -k is supposed to do. You'd want -m or pipe it from the> message list, then it includes the headers.
The -k flag prevents git from remove parts of the message Subject while
parsing the commit message from it
I just noticed using `:pipe cat` that the piped message has no Subject,
or any other header except `From`. Might this be a misconfiguration?
Cheers,
Oscar
Hi Oscar,
'Oscar Campos', Apr 09, 2023 at 17:15:
> I just noticed using `:pipe cat` that the piped message has no Subject,> or any other header except `From`. Might this be a misconfiguration?
:pipe only outputs the selected message part by default (unless used
from the message list). If you want to pipe the full message, use the -m
flag as described in the man page:
https://git.sr.ht/~rjarry/aerc/tree/master/item/doc/aerc.1.scd#L226-232
Hi Robin,
On Sun Apr 9, 2023 at 4:29 PM IST, Robin Jarry wrote:
> :pipe only outputs the selected message part by default (unless used> from the message list). If you want to pipe the full message, use the -m> flag as described in the man page:
Gotcha, now I understand what Moritz meant with -m, I thouht he was
speaking about the `git am` command (and I suspect he thought I was
speaking about the :pipe command when I mentioned I used -k earlier)
Thanks for the tip, everything works fine now
Keep up the fantastic job btw.
Cheers,
Oscar