From: Mark Wielaard <mark@klomp.org>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: Tom Tromey <tom@tromey.com>, Luis Machado <luis.machado@arm.com>,
Simon Marchi <simark@simark.ca>,
"gdb@sourceware.org" <gdb@sourceware.org>,
John Baldwin <jhb@FreeBSD.org>
Subject: Re: Any concrete plans after the GDB BoF?
Date: Mon, 30 Jan 2023 19:46:51 +0100 [thread overview]
Message-ID: <20230130184651.GG11361@gnu.wildebeest.org> (raw)
In-Reply-To: <20230130174318.m2itnzacnbbtxdl6@ubuntu.lan>
Hi,
On Mon, Jan 30, 2023 at 05:43:18PM +0000, Lancelot SIX wrote:
> > Lancelot> That being said, I still use git-pw to fetch and apply patch and series.
> > Lancelot> This is really convenient when I am not working on the host where I have
> > Lancelot> my mail client.
> >
> > Have you tried b4 instead? I haven't yet but it seems like the same
> > thing but without needing patchwork, just public inbox.
> >
> > https://b4.docs.kernel.org/en/latest/index.html
>
> I haven't yet either. For now git-pw seems to allow me to do what I am
> trying to achieve. I'll still try to have a closer look at b4 to check
> if it can provide a better experience.
b4 acts a little different from git-pw. It uses Message-IDs to fetch
patches (and/or a whole thread as mbox). So it helps if your mta
displays those prominently. If you use emacs you might be interested
in piem: https://git.kyleam.com/piem/about/
For gdb-patches you want to add the following to your .git/config:
[b4]
midmask = https://inbox.sourceware.org/gdb-patches/%s
linkmask = https://inbox.sourceware.org.org/gdb-patches/%s
There is a command line example in this presentation:
https://gnu.wildebeest.org/~mark/fsf-sourceware/presentation.html#slide14
The latest b4 can also interact with patchwork, but I haven't tried
that out yet. The new settings are described at:
https://b4.docs.kernel.org/en/latest/config.html#patchwork-integration-settings
Cheers,
Mark
next prev parent reply other threads:[~2023-01-30 18:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 10:47 Luis Machado
2022-10-28 16:16 ` Simon Marchi
2022-10-28 16:51 ` John Baldwin
2022-10-28 16:54 ` Simon Marchi
2022-10-31 9:28 ` Luis Machado
2022-10-31 13:17 ` Simon Marchi
2022-10-31 13:37 ` Joel Brobecker
2022-10-31 14:15 ` Simon Marchi
2022-10-31 17:31 ` Joel Brobecker
2023-02-11 17:13 ` Andrew Burgess
2023-02-12 12:43 ` Mark Wielaard
2023-02-13 11:54 ` Andrew Burgess
2023-02-13 12:52 ` Luis Machado
2023-02-13 14:24 ` Tom Tromey
2023-02-13 14:42 ` Luis Machado
2023-02-13 15:13 ` Andrew Burgess
2023-02-13 15:23 ` Luis Machado
2023-02-14 5:48 ` Joel Brobecker
2023-02-15 14:47 ` Andrew Burgess
2023-02-16 4:14 ` Joel Brobecker
2023-02-16 9:51 ` Mark Wielaard
2023-02-16 10:16 ` Joel Brobecker
2023-02-16 11:58 ` Eli Zaretskii
2023-02-16 13:31 ` Joel Brobecker
2023-02-16 15:23 ` Eli Zaretskii
2023-02-14 13:07 ` Mark Wielaard
2023-02-14 14:23 ` Pedro Alves
2023-02-14 13:00 ` Mark Wielaard
2023-02-15 14:36 ` Andrew Burgess
2023-02-13 14:05 ` Tom Tromey
2022-12-15 10:17 ` Luis Machado
2023-01-01 22:02 ` Mark Wielaard
2023-01-20 17:30 ` Tom Tromey
2023-01-20 20:30 ` Tom Tromey
2023-01-27 15:50 ` Lancelot SIX
2023-01-27 23:50 ` Tom Tromey
2023-01-30 17:43 ` Lancelot SIX
2023-01-30 18:46 ` Mark Wielaard [this message]
2023-01-30 21:08 ` Tom Tromey
2023-02-04 11:36 ` Mark Wielaard
2023-01-31 10:00 ` Lancelot SIX
2022-12-13 2:48 ` Frank Ch. Eigler
2023-02-16 8:53 anix
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=20230130184651.GG11361@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=gdb@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=lsix@lancelotsix.com \
--cc=luis.machado@arm.com \
--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).