From: Andreas Ericsson <ae@op5.se>
To: "Uwe Kleine-König" <ukleinek@strlen.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org, "Randal L. Schwartz" <merlyn@stonehenge.com>
Subject: Re: [RFC] git rev-contains [Was: merge -s ffonly]
Date: Wed, 08 Oct 2008 08:18:48 +0200 [thread overview]
Message-ID: <48EC50C8.4000603@op5.se> (raw)
In-Reply-To: <20081007185815.GA10744@strlen.de>
Uwe Kleine-König wrote:
> 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.)
>
On Linux (well, on my system anyways), it's 128K for arguments and
environment combined.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-10-08 6:20 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 ` [RFC] git rev-contains [Was: merge -s ffonly] Uwe Kleine-König
2008-10-08 6:18 ` Andreas Ericsson [this message]
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=48EC50C8.4000603@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=spearce@spearce.org \
--cc=ukleinek@strlen.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).