git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 0/6] git-name-rev -d and git-describe improvements
Date: Sun, 24 Feb 2008 03:07:14 -0500	[thread overview]
Message-ID: <20080224080714.GH8410@spearce.org> (raw)

This series of 6 patches improves performance for both describe and
`show-ref -d` on repositories with a lot of tags, and finally ends
with the display of the current tag for detached HEAD in the bash
prompt rather than the abbreviated SHA-1.

The `show-ref -d` improvements should help both gitk and gitweb
performance as it reduces the total number of lstats necessary
(we were doing an extra unnecessary lstat on each packed ref).

The `describe --exact-match` flag is useful in scripts, as shown
by the final patch in the series.

  1) Protect peel_ref fallback case from NULL parse_object result
  2) Optimize peel_ref for the current ref of a for_each_ref callback
  3) Teach git-describe to use peeled ref information when scanning tags
  4) Avoid accessing non-tag refs in git-describe unless --all is requested
  5) Teach git-describe --exact-match to avoid expensive tag searches
  6) Use git-describe --exact-match in bash prompt on detached HEAD

 Documentation/git-describe.txt         |    5 ++++
 builtin-describe.c                     |   35 ++++++++++++++++++++++++-------
 contrib/completion/git-completion.bash |    5 +++-
 refs.c                                 |   27 +++++++++++++++++++-----
 4 files changed, 57 insertions(+), 15 deletions(-)

-- 
Shawn.

                 reply	other threads:[~2008-02-24  8:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080224080714.GH8410@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 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).