From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Patchew: 'Based-on' tag for ongoing work dependence
Date: Fri, 3 May 2024 13:18:40 +0200 [thread overview]
Message-ID: <9b1d1d79-6c11-438d-a72a-7ba360cce87e@kernel.org> (raw)
Hello,
When looking for something, I noticed [1] that Patchew accepts the
'Based-on' tag to deal with dependences.
If patches depend on other ongoing work that has not been applied yet,
the cover-letter (or the individual patch) should contain a tag line
"Based-on: <$MESSAGE_ID>", so Patchew can resolve the dependence, and
trigger the CI. I just updated our wiki about that [2].
[1]
https://qemu.readthedocs.io/en/v9.0.0/devel/submitting-a-patch.html#base-patches-against-current-git-master
[2] https://github.com/multipath-tcp/mptcp_net-next/wiki/CI#base-patches
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
reply other threads:[~2024-05-03 11:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9b1d1d79-6c11-438d-a72a-7ba360cce87e@kernel.org \
--to=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
/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).