From: Jonathan Corbet <corbet@lwn.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: b4 and git am -s errors (was Re: [PATCH 1/2] ext4: docs: switch away from list-table)
Date: Thu, 07 Oct 2021 13:11:11 -0600 [thread overview]
Message-ID: <87fstczm40.fsf@meer.lwn.net> (raw)
In-Reply-To: <20211007182257.tj6vrjgfusizv3ml@meerkat.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> On Thu, Oct 07, 2021 at 12:06:00PM -0600, Jonathan Corbet wrote:
>> My script is still "b4 am | git am", haven't tried shazam yet - it's
>> definitely on the radar, though.
>
> Okay, now I'm curious which version of git this is, since I can't seem to
> replicate this problem -- I just get:
>
> - multiple identical Signed-off-by lines if my S-o-b is not the last
> - nothing added to trailers if my S-o-b is already the last trailer
2.31.1, as packaged by Fedora. b4 0.8.0 from PyPI, for what that's worth.
Specifically, I do:
b4 am -o ~/tmp -n am -c -t 20210902220854.198850-1-corbet@lwn.net
git am -a ~/tmp/am.mbx
...and that prints "Duplicate Signed-off-by lines." and leaves the repo
in the "in the middle of an am session" state.
jon
next prev parent reply other threads:[~2021-10-07 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210902220854.198850-1-corbet@lwn.net>
[not found] ` <20210902220854.198850-2-corbet@lwn.net>
[not found] ` <20210916095455.GE10610@quack2.suse.cz>
[not found] ` <877df9tt5d.fsf@meer.lwn.net>
[not found] ` <YV8EGFcPtM9u+ihl@mit.edu>
[not found] ` <87wnmozy9i.fsf@meer.lwn.net>
2021-10-07 17:38 ` b4 and git am -s errors (was Re: [PATCH 1/2] ext4: docs: switch away from list-table) Konstantin Ryabitsev
2021-10-07 18:06 ` Jonathan Corbet
2021-10-07 18:22 ` Konstantin Ryabitsev
2021-10-07 19:11 ` Jonathan Corbet [this message]
2021-10-07 19:18 ` Konstantin Ryabitsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fstczm40.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox