git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v2 0/9] Extending the shelf-life of "git describe" output
Date: Wed, 20 Jun 2012 23:35:23 -0700	[thread overview]
Message-ID: <1340260532-11378-1-git-send-email-gitster@pobox.com> (raw)

This is take 2.  The first round was $gmane/200165.

A major difference from v1 is the [PATCH 6/9].  The earlier approach
was to filter out candidates that match the given prefix for
additional criteria as they are found in the loop, but this round
tries to optimize for the common case of not having ambiguities.  We
postpone running additional test until we find the second object
that match the prefix (in other words, if there is only one object
that has the prefix, we do not apply the "we know this name refers
to a commit" hint, and let the caller deal with a non commit object,
just like the current code does).

Junio C Hamano (9):
  sha1_name.c: indentation fix
  sha1_name.c: clarify what "fake" is for in find_short_object_filename()
  sha1_name.c: rename "now" to "current"
  sha1_name.c: refactor find_short_packed_object()
  sha1_name.c: correct misnamed "canonical" and "res"
  sha1_name.c: restructure disambiguation of short names
  sha1_name.c: allow get_short_sha1() to take other flags
  sha1_name.c: teach get_short_sha1() a commit-only option
  sha1_name.c: get_describe_name() by definition groks only commits

 sha1_name.c | 282 +++++++++++++++++++++++++++++++++++++++---------------------
 1 file changed, 182 insertions(+), 100 deletions(-)

-- 
1.7.11.2.gd284367

             reply	other threads:[~2012-06-21  6:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21  6:35 Junio C Hamano [this message]
2012-06-21  6:35 ` [PATCH v2 1/9] sha1_name.c: indentation fix Junio C Hamano
2012-06-21  6:35 ` [PATCH v2 2/9] sha1_name.c: clarify what "fake" is for in find_short_object_filename() Junio C Hamano
2012-06-21  6:35 ` [PATCH v2 3/9] sha1_name.c: rename "now" to "current" Junio C Hamano
2012-06-21  6:35 ` [PATCH v2 4/9] sha1_name.c: refactor find_short_packed_object() Junio C Hamano
2012-06-21  6:35 ` [PATCH v2 5/9] sha1_name.c: correct misnamed "canonical" and "res" Junio C Hamano
2012-06-21  6:35 ` [PATCH v2 6/9] sha1_name.c: restructure disambiguation of short names Junio C Hamano
2012-06-21  6:35 ` [PATCH v2 7/9] sha1_name.c: allow get_short_sha1() to take other flags Junio C Hamano
2012-06-21  6:35 ` [PATCH v2 8/9] sha1_name.c: teach get_short_sha1() a commit-only option Junio C Hamano
2012-06-21  6:35 ` [PATCH v2 9/9] sha1_name.c: get_describe_name() by definition groks only commits Junio C Hamano
2012-06-21  9:22   ` Erik Faye-Lund
2012-06-21 19:57     ` Junio C Hamano

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=1340260532-11378-1-git-send-email-gitster@pobox.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).