From: Guinevere Larsen <blarsen@redhat.com>
To: Carl Love <cel@linux.ibm.com>,
Luis Machado <luis.machado@arm.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
gdb-patches@sourceware.org
Cc: Pedro Alves <pedro@palves.net>, Tom Tromey <tom@tromey.com>,
Simon Marchi <simark@simark.ca>
Subject: Re: [ PATCH 0/3] Fix GDB reverse execution behavior
Date: Thu, 30 Nov 2023 16:45:39 +0100 [thread overview]
Message-ID: <deb29957-643d-f4af-b91f-329bd67c41c8@redhat.com> (raw)
In-Reply-To: <85a2f33d4ad12966dcb212e99e836175b69fddee.camel@linux.ibm.com>
On 30/11/2023 16:39, Carl Love wrote:
> Guinevere:
>
> On Thu, 2023-11-30 at 12:36 +0100, Guinevere Larsen wrote:
>> On a side note, b4 didn't really like this series and I'm not sure
>> why.
>> My guess is that all 3 patches have the same email subject, but it
>> may
>> also be that I needed --3way when using git am. Either way, just
>> mentioning to gather knowledge on what b4 likes or doesn't like.
>
> I am not familiar with b4. I just did a Google search and found a
> description of it at:
>
> https://people.kernel.org/monsieuricon/introducing-b4-and-patch-attestation
>
> It seems to be a tool the maintainers can use for patch management. I
> will have to play around with it and see if I can figure out why b4
> doesn't like the patch series.
>
> Is this something that people have started using?
>
We started talking about this because it automatically collects the git
trailers and applies them, so you wouldn't need to change your local
commits, and makes it easy for reviewers. Simon wrote some tips about
using it in the wiki a little bit ago:
https://sourceware.org/gdb/wiki/DeveloperTips#Downloading_and_applying_patches_from_the_mailing_list
It's not required or anything, it's just handy.
I like to use it as "b4 shazam <message-id>" which would automatically
apply the patches, not just download them. Maybe that's where it went
wrong...
--
Cheers,
Guinevere Larsen
She/Her/Hers
next prev parent reply other threads:[~2023-11-30 15:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f624c5566d6a8a1014ecc38900ca1ba0202989ef.camel@linux.ibm.com>
[not found] ` <890101c23dd5fa60fcbf9d4b299cb2a533c260b7.camel@linux.ibm.com>
[not found] ` <1e702d8f-e5b4-4719-b1e7-42210f350305@arm.com>
[not found] ` <a01f4e5f3fd399e3a9a971421265b34d08e32388.camel@linux.ibm.com>
[not found] ` <643afce1-ab9b-4e8b-bcbb-5738dc409a28@arm.com>
[not found] ` <9e17008084c34f953f5318933436ec703250120a.camel@linux.ibm.com>
[not found] ` <92a751d1-a4b9-4c21-821e-a1dc67207516@arm.com>
[not found] ` <ee4ed81911a3196327c2aea3fa9a77f910a5e798.camel@linux.ibm.com>
2023-11-22 23:33 ` Carl Love
2023-11-30 11:36 ` Guinevere Larsen
2023-11-30 15:39 ` Carl Love
2023-11-30 15:43 ` Luis Machado
2023-12-11 14:40 ` Luis Machado
2023-12-14 16:10 ` Carl Love
2024-01-02 22:52 ` Carl Love
2023-11-30 15:45 ` Guinevere Larsen [this message]
2023-11-22 23:33 ` [ PATCH 1/3] " Carl Love
2023-11-29 11:44 ` Luis Machado
2023-11-29 16:30 ` Carl Love
2023-11-29 16:38 ` Luis Machado
2023-11-22 23:33 ` [ PATCH 2/3] " Carl Love
2023-11-29 11:44 ` Luis Machado
2023-11-22 23:33 ` [PATCH 3/3] " Carl Love
2023-11-29 11:46 ` Luis Machado
2023-11-29 16:30 ` Carl Love
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=deb29957-643d-f4af-b91f-329bd67c41c8@redhat.com \
--to=blarsen@redhat.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=cel@linux.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=pedro@palves.net \
--cc=simark@simark.ca \
--cc=tom@tromey.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).