All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: "Anders Höckersten via GitGitGadget" <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Cc: "Bagas Sanjaya" <bagasdotme@gmail.com>,
	"Felipe Contreras" <felipe.contreras@gmail.com>,
	"Robert P. J. Day" <rpjday@crashcourse.ca>,
	"Anders Höckersten" <anders@hockersten.se>
Subject: Re: [PATCH v2] describe-doc: clarify default length of abbreviation
Date: Mon, 17 May 2021 12:44:58 -0400	[thread overview]
Message-ID: <4d101a5d-3ee7-5601-2de1-4a8afeeaaec4@gmail.com> (raw)
In-Reply-To: <pull.1026.v2.git.git.1621230831465.gitgitgadget@gmail.com>

On 5/17/2021 1:53 AM, Anders Höckersten via GitGitGadget wrote:
> From: =?UTF-8?q?Anders=20H=C3=B6ckersten?= <anders@hockersten.se>
> 
> Clarify the default length used for the abbreviated form used for
> commits in git describe.
> 
> The behavior was modified in Git 2.11.0, but the documentation was not
> updated to clarify the new behavior.

I'm a bit late to the party, but am interested in our abbreviation
code. I found these updates to be sensible, and that you appropriately
adjusted from v1 according to the feedback.

Thanks,
-Stolee

      reply	other threads:[~2021-05-17 16:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16  7:32 [PATCH] describe-doc: clarify default length of abbreviation Anders Höckersten via GitGitGadget
2021-05-16 11:34 ` Junio C Hamano
2021-05-16 12:00 ` Bagas Sanjaya
2021-05-16 12:47   ` Anders Höckersten
2021-05-16 12:58     ` Junio C Hamano
2021-05-17  5:51       ` Anders Höckersten
2021-05-16 18:51   ` Felipe Contreras
2021-05-16 19:00     ` Robert P. J. Day
2021-05-16 21:07       ` Felipe Contreras
2021-05-17  5:53 ` [PATCH v2] " Anders Höckersten via GitGitGadget
2021-05-17 16:44   ` Derrick Stolee [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=4d101a5d-3ee7-5601-2de1-4a8afeeaaec4@gmail.com \
    --to=stolee@gmail.com \
    --cc=anders@hockersten.se \
    --cc=bagasdotme@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=rpjday@crashcourse.ca \
    /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.