From: Shrikanth Hegde <sshegde@linux.vnet.ibm.com>
To: tools@linux.kernel.org
Subject: b4: request for adding support to get older revisions in b4 mbox
Date: Tue, 4 Apr 2023 16:18:35 +0530 [thread overview]
Message-ID: <2b01caf0-2a58-b21e-2b0f-5528aec16631@linux.vnet.ibm.com> (raw)
Currently, the b4 mbox has a way to check for newer revisions.
b4 mbox --help
<...>
-c, --check-newer-revisions
Check if newer patch revisions exist
This would help to pull the later versions if exists based on the message-id.
This works as expected. If V1 of the series, it can pull all the way to latest.
That is nice.
Pulling an older version of a PATCH series given a message-id is also very
helpful. Quite often we come across a latest version of a patch series and
cover letter points that issue is described in details in V1 or V2 or so.
Finding that V1 might be tricky and take a bit of search.
Can we have that support? Does it make any sense?
Thanks
Shrikanth
next reply other threads:[~2023-04-04 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 10:48 Shrikanth Hegde [this message]
2023-04-24 5:31 ` b4: request for adding support to get older revisions in b4 mbox Shrikanth Hegde
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=2b01caf0-2a58-b21e-2b0f-5528aec16631@linux.vnet.ibm.com \
--to=sshegde@linux.vnet.ibm.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).