Re: What's cooking in git.git (Oct 2019, #01; Thu, 3)

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 5, 2019, 23:36 UTC
Message-ID: <xmqqzhie69yz.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <972f4674-ed00-7113-24eb-f59f1b751690@gmail.com>

Phillip Wood <phillip.wood123@gmail.com> writes:

Show 11 quoted lines

>> * ra/rebase-i-more-options (2019-09-09) 6 commits
>> ...
>>   Is this ready for 'next'.
>
> Nearly, but not quite I think cf [1]. Also I'm still not convinced
> that having different behaviors for --ignore-whitespace depending on
> the backend is going to be helpful but maybe they are close enough not
> to matter too much in practice [2].
>
> [1]
> https://public-inbox.org/git/20190806173638.17510-1-rohit.ashiwal265@gmail.com/T/#m965ce1f09d1d1b8010c04db0eabd4b19ce99fe82

OK, so I'll leave a note that this needs to consider existing GIT_COMMITTER_DATE environment variable, etc, with a reference to <5adde732-173b-d24d-d23f-bb4d043076d7@gmail.com>.

A URL to public-inbox.org is good, but that is because those who do not use public-inbox.org (or after the site goes out of service) can still identify exactly which message you are referring to if you use the https://public-inbox.org/git/$message_id_without_brackets format.

Unlike that form, the format you used only identifies the thread starter, and without public-inbox.org in service, a reader cannot tell which message in the thread you are referring to, even if the reader had full mailing list archive.

IOW, I would have appreciated if the above reference were done like so:

 https://public-inbox.org/git/5adde732-173b-d24d-d23f-bb4d043076d7@gmail.com/

Thanks.