All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2019, #01; Thu, 3)
Date: Sun, 06 Oct 2019 08:36:36 +0900	[thread overview]
Message-ID: <xmqqzhie69yz.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <972f4674-ed00-7113-24eb-f59f1b751690@gmail.com> (Phillip Wood's message of "Fri, 4 Oct 2019 10:44:47 +0100")

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

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

      parent reply	other threads:[~2019-10-05 23:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03  5:04 What's cooking in git.git (Oct 2019, #01; Thu, 3) Junio C Hamano
2019-10-03 18:28 ` Emily Shaffer
2019-10-03 22:31   ` Junio C Hamano
2019-10-03 20:28 ` Elijah Newren
2019-10-03 22:31   ` Junio C Hamano
2019-10-04  9:44 ` Phillip Wood
2019-10-05  0:40   ` Elijah Newren
2019-10-05 19:46     ` Phillip Wood
2019-10-05 23:36   ` Junio C Hamano [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=xmqqzhie69yz.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=phillip.wood123@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.