Re: [PATCH] doc: explain the impact of stash.index on --autostash options

From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Date: Oct 13, 2025, 12:17 UTC
Message-ID: <d4dc8042-b996-4889-88cb-f0862a12d09c@app.fastmail.com>
In-Reply-To: <B78CD1B1-67C1-4EA1-94A7-13AD40C43585@gmail.com>

On Sun, Oct 12, 2025, at 20:04, Ben Knoble wrote:

Show 12 quoted lines

>>>[snip]
>>
>> Yeah, that is less useful to me (there is a tool, given a commit
>> object, to figure out at which merge it got merged to the mainline);
>> I didn't think of a way the information can be useful to general
>> readers.  If the mainline merge was a release or more ago, then it
>> may make sense to say "commit X, which appeared in version Y, was
>> broken in such and such way, and here is to fix its breakage"
>
> It’s not clear to me if you’d like to see a v2 or not, but given you
> were already happy to merge in the latest what’s cooking, I don’t mind
> not sending one ;)

Sorry. I misread a What’s Cooking email[1] as asking why a topic hadn’t been picked up. But you were asking about sending another patch on top of something which was already in `next`.

I wouldn’t have sent that email if I knew it was already in `next` (if I had checked better).