From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: RFC: indicating diff strategy in format-patch message headers
Date: Sun, 16 Jun 2024 23:47:41 +0000 [thread overview]
Message-ID: <20240616234741.M713118@dcvr> (raw)
In-Reply-To: <20240607-ultra-unicorn-of-democracy-d25a69@lemur>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Wed, Jun 05, 2024 at 10:26:58PM GMT, Eric Wong wrote:
> > > That would be redundant with the message-id. Unfortunately, this doesn't solve
> > > the problem of how to reliably map a commit to the patch from which it
> > > originated, other than using the Message-ID: or Link: trailers.
> >
> > dfpre:, dfblob:, dfpost: search queries on lore seem to work...
>
> I've thought about that, but this is also not very reliable, at least not when
> patch series are applied as fast-forwards, not merges. Unfortunately, some
> projects enforce a flat history (glibc, gcc), with merges being specifically
> not allowed -- which means dfblob matching is not going to match a lot of
> commits.
Yeha, my initial plan (way back around 2016 or 2017) was to use
Subject; but I also forgot why I stopped with that idea :x
Anyways, trying to add bs: (body+subject) to queries in addition to dfblob
may prove useful:
https://public-inbox.org/meta/20240616233532.574646-1-e@80x24.org/
Not sure if author + date is necessary...
prev parent reply other threads:[~2024-06-16 23:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 18:01 RFC: indicating diff strategy in format-patch message headers Konstantin Ryabitsev
2024-06-05 18:22 ` Junio C Hamano
2024-06-05 18:46 ` Konstantin Ryabitsev
2024-06-05 22:26 ` Eric Wong
2024-06-07 19:53 ` Konstantin Ryabitsev
2024-06-16 23:47 ` Eric Wong [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=20240616234741.M713118@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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;
as well as URLs for NNTP newsgroup(s).