From: Sandra Snan <sandra.snan@idiomdrottning.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: git@vger.kernel.org
Subject: Re: getting git send-email patches from someone who is behind
Date: Fri, 08 Dec 2023 19:57:33 +0100 [thread overview]
Message-ID: <87a5qkjzdu.fsf@ellen.idiomdrottning.org> (raw)
In-Reply-To: <20231208-amusing-vengeful-raptor-e71a8b@meerkat>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> Yes, setting base-commit is the right solution here -- it will
> tell you exactly where in the tree it belongs.
I didn't know that before today and that's good advice when
sending patches, but if I'm receiving patches without that field
set, I wonder how people are dealing with that.
> In its absence, tools like b4 will also try to guess where the
> series might belong by comparing the file index information
> mentioned in the patches.
Ah, this! https://b4.docs.kernel.org/en/latest/
This looks wonderful, thank you!
prev parent reply other threads:[~2023-12-08 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 17:50 getting git send-email patches from someone who is behind Sandra Snan
2023-12-08 18:49 ` Konstantin Ryabitsev
2023-12-08 18:57 ` Sandra Snan [this message]
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=87a5qkjzdu.fsf@ellen.idiomdrottning.org \
--to=sandra.snan@idiomdrottning.org \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.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