From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Cc: "Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Andrew Melnychenko" <andrew@daynix.com>,
"Jason Wang" <jasowang@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
alex.bennee@linaro.org,
"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
"Fabiano Rosas" <farosas@suse.de>,
"Kevin Wolf" <kwolf@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
qemu-arm@nongnu.org,
"Yuri Benditovich" <yuri.benditovich@daynix.com>,
manos.pitsidianakis@linaro.org, qemu-block@nongnu.org,
"Michael Roth" <michael.roth@amd.com>,
"Konstantin Kostiuk" <kkostiuk@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
gustavo.romero@linaro.org,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH 3/7] docs/devel: add b4 for patch retrieval
Date: Tue, 19 Nov 2024 10:07:46 +0000 [thread overview]
Message-ID: <ZzxjciUGNIVoUuVC@redhat.com> (raw)
In-Reply-To: <47831adc-26f7-4633-a371-975c97e8dae7@linaro.org>
On Tue, Nov 19, 2024 at 10:56:36AM +0100, Marcin Juszkiewicz wrote:
> W dniu 19.11.2024 o 10:14, Daniel P. Berrangé pisze:
>
> > > + b4 shazam $msg-id
> >
> > I'm wondering how b4 knows where to find the mails for $msg-id for QEMU ?
>
> It goes for https://lore.kernel.org/qemu-devel/$msg-id by default or checks
> b4.midmask in git config.
How does it figure out to look at '/qemu-devel/' by default ?
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-11-19 10:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 17:23 [PATCH 0/7] Enhance documentation for new developers Pierrick Bouvier
2024-11-18 17:23 ` [PATCH 1/7] docs/devel: remove dead video link for sourcehut submit process Pierrick Bouvier
2024-11-19 8:25 ` Thomas Huth
2024-11-18 17:23 ` [PATCH 2/7] docs/devel: add git-publish for patch submitting Pierrick Bouvier
2024-11-19 8:41 ` Marcin Juszkiewicz
2024-11-19 9:12 ` Daniel P. Berrangé
2024-11-20 6:29 ` Pierrick Bouvier
2024-11-20 6:25 ` Pierrick Bouvier
2024-11-20 9:51 ` Alex Bennée
2024-11-20 10:01 ` Daniel P. Berrangé
2024-11-19 9:04 ` Daniel P. Berrangé
2024-11-20 21:45 ` Pierrick Bouvier
2024-11-18 17:23 ` [PATCH 3/7] docs/devel: add b4 for patch retrieval Pierrick Bouvier
2024-11-19 9:14 ` Daniel P. Berrangé
2024-11-19 9:56 ` Marcin Juszkiewicz
2024-11-19 10:07 ` Daniel P. Berrangé [this message]
2024-11-19 10:40 ` Marcin Juszkiewicz
2024-11-18 17:23 ` [PATCH 4/7] docs/devel: add information on how to setup build environments Pierrick Bouvier
2024-11-19 9:24 ` Daniel P. Berrangé
2024-11-19 11:08 ` Alex Bennée
2024-11-19 11:16 ` Daniel P. Berrangé
2024-11-20 21:58 ` Pierrick Bouvier
2024-11-18 17:23 ` [PATCH 5/7] docs: add a codebase section Pierrick Bouvier
2024-12-03 15:53 ` Peter Maydell
2024-12-03 17:22 ` Alex Bennée
2024-12-03 17:46 ` Peter Maydell
2024-12-03 19:35 ` Pierrick Bouvier
2024-12-04 8:58 ` Daniel P. Berrangé
2024-12-03 21:02 ` Pierrick Bouvier
2024-11-18 17:23 ` [PATCH 6/7] docs: add a glossary Pierrick Bouvier
2024-12-03 17:37 ` Peter Maydell
2024-12-03 18:10 ` Alex Bennée
2024-12-03 19:37 ` Pierrick Bouvier
2024-12-03 20:32 ` Pierrick Bouvier
2024-12-05 15:23 ` Peter Maydell
2024-12-05 19:21 ` Pierrick Bouvier
2024-11-18 17:23 ` [PATCH 7/7] docs: add a how to section Pierrick Bouvier
2024-11-19 9:29 ` Daniel P. Berrangé
2024-11-20 22:05 ` Pierrick Bouvier
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=ZzxjciUGNIVoUuVC@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=andrew@daynix.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=gustavo.romero@linaro.org \
--cc=jasowang@redhat.com \
--cc=kkostiuk@redhat.com \
--cc=kwolf@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=vsementsov@yandex-team.ru \
--cc=yuri.benditovich@daynix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.