Re: RFC: indicating diff strategy in format-patch message headers

From: Eric Wong <e@80x24.org>
Date: Jun 16, 2024, 23:47 UTC
Message-ID: <20240616234741.M713118@dcvr>
In-Reply-To: <20240607-ultra-unicorn-of-democracy-d25a69@lemur>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:

Show 12 quoted lines

> 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...