From: "Uwe Kleine-König" <ukleinek@strlen.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, "Randal L. Schwartz" <merlyn@stonehenge.com>
Subject: [RFC] git rev-contains [Was: merge -s ffonly]
Date: Tue, 7 Oct 2008 20:58:15 +0200 [thread overview]
Message-ID: <20081007185815.GA10744@strlen.de> (raw)
In-Reply-To: <20081006235611.GA17662@spearce.org>
Hello,
> + if test -n "$(git rev-list $1..HEAD)"
I already wrote similar tests and I wonder if this couldn't be done in a
new builtin command more effectively. Something like
git rev-contains HEAD "$1"
. I expect it to be faster and maybe it prevents a command line
overflow?! (I remember something like 32000 chars max in a command, but
I could not trigger that with bash.)
Best regards
Uwe
next prev parent reply other threads:[~2008-10-07 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 23:56 merge -s ffonly Shawn O. Pearce
2008-10-07 18:58 ` Uwe Kleine-König [this message]
2008-10-08 6:18 ` [RFC] git rev-contains [Was: merge -s ffonly] Andreas Ericsson
2008-10-08 14:30 ` Deskin Miller
2008-10-08 15:41 ` Uwe Kleine-König
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=20081007185815.GA10744@strlen.de \
--to=ukleinek@strlen.de \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--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 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).