From: "Shawn O. Pearce" <spearce@spearce.org>
To: SZEDER GGGbor <szeder@ira.uka.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] bash: use for-each-ref format 'refname:short'
Date: Fri, 19 Sep 2008 16:51:54 -0700 [thread overview]
Message-ID: <20080919235154.GE13139@spearce.org> (raw)
In-Reply-To: <1221862525-20574-1-git-send-email-szeder@ira.uka.de>
SZEDER GGGbor <szeder@ira.uka.de> wrote:
> Using this format simplifies the code for completing refs and (in some
> cases) improves performance significantly.
>
> For repositories like the current git.git (with more than 200 refs)
> there is no real performance difference, but for a repository with 2000
> refs the total time needed to complete the refs is reduced by ~25% (from
> around 400ms to around 305ms).
>
> Signed-off-by: SZEDER Gábor <szeder@ira.uka.de>
Nice improvement.
Acked-by: Shawn O. Pearce <spearce@spearce.org>
> OK, so after the refname:short patch hit master, here is the updated
> patch to use it in bash completion. The patch itself is the same as
> the original one, except, of course, the for-each-ref format name. I
> have also adjusted the performance numbers in the commit message.
>
> contrib/completion/git-completion.bash | 26 ++++++--------------------
> 1 files changed, 6 insertions(+), 20 deletions(-)
>
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index d3fb6ae..fccb499 100755
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -154,11 +154,8 @@ __git_heads ()
> {
> local cmd i is_hash=y dir="$(__gitdir "$1")"
> if [ -d "$dir" ]; then
> - for i in $(git --git-dir="$dir" \
> - for-each-ref --format='%(refname)' \
> - refs/heads ); do
> - echo "${i#refs/heads/}"
> - done
> + git --git-dir="$dir" for-each-ref --format='%(refname:short)' \
> + refs/heads
> return
> fi
> for i in $(git ls-remote "$1" 2>/dev/null); do
> @@ -175,11 +172,8 @@ __git_tags ()
> {
> local cmd i is_hash=y dir="$(__gitdir "$1")"
> if [ -d "$dir" ]; then
> - for i in $(git --git-dir="$dir" \
> - for-each-ref --format='%(refname)' \
> - refs/tags ); do
> - echo "${i#refs/tags/}"
> - done
> + git --git-dir="$dir" for-each-ref --format='%(refname:short)' \
> + refs/tags
> return
> fi
> for i in $(git ls-remote "$1" 2>/dev/null); do
> @@ -197,16 +191,8 @@ __git_refs ()
> local cmd i is_hash=y dir="$(__gitdir "$1")"
> if [ -d "$dir" ]; then
> if [ -e "$dir/HEAD" ]; then echo HEAD; fi
> - for i in $(git --git-dir="$dir" \
> - for-each-ref --format='%(refname)' \
> - refs/tags refs/heads refs/remotes); do
> - case "$i" in
> - refs/tags/*) echo "${i#refs/tags/}" ;;
> - refs/heads/*) echo "${i#refs/heads/}" ;;
> - refs/remotes/*) echo "${i#refs/remotes/}" ;;
> - *) echo "$i" ;;
> - esac
> - done
> + git --git-dir="$dir" for-each-ref --format='%(refname:short)' \
> + refs/tags refs/heads refs/remotes
> return
> fi
> for i in $(git ls-remote "$dir" 2>/dev/null); do
--
Shawn.
prev parent reply other threads:[~2008-09-19 23:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 22:15 [PATCH] bash: use for-each-ref format 'refname:short' SZEDER Gábor
2008-09-19 23:51 ` Shawn O. Pearce [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=20080919235154.GE13139@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder@ira.uka.de \
/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).