From: Junio C Hamano <junkio@cox.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/10] Teach git-completion.bash how to complete git-merge.
Date: Mon, 27 Nov 2006 11:12:40 -0800 [thread overview]
Message-ID: <7vlklwhffb.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20061127084047.GA19745@spearce.org
"Shawn O. Pearce" <spearce@spearce.org> writes:
> +__git_merge_strategies ()
> +{
> + sed -n "/^all_strategies='/{
> + s/^all_strategies='//
> + s/'//
> + p
> + q
> + }" "$(git --exec-path)/git-merge"
> +}
> +
Shouldn't we load and compute this once and keep the result in a
variable (say $__git_merge_strategies)?
next prev parent reply other threads:[~2006-11-27 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 8:40 [PATCH 1/10] Teach git-completion.bash how to complete git-merge Shawn O. Pearce
2006-11-27 19:12 ` Junio C Hamano [this message]
2006-11-27 20:12 ` Shawn Pearce
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=7vlklwhffb.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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 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.