From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Junio C Hamano" <junkio@cox.net>,
"Andy Parkins" <andyparkins@gmail.com>,
"Bill Lear" <rael@zopyra.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Split sample update hook into post-receive hook
Date: Thu, 8 Mar 2007 13:09:07 +0100 [thread overview]
Message-ID: <81b0412b0703080409u5ae64698tfa70a8ba2de65df@mail.gmail.com> (raw)
In-Reply-To: <20070308100237.GF30289@spearce.org>
On 3/8/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> > The proprietary OS' will have the problem, though. And far sooner
> > than 1300 refs (w2k has only 32767 bytes for command line).
> > Besides, don't overestimate peoples readiness to be careful
> > about reference names. I would expect reference names over
> > 100 bytes in length to happen regularly (generated from file names
> > appended with a timestamp, for example).
>
> Cygwin's lifted that argument handling to be unlimited.
Actually, it didn't at all. Cygwin conveniently forgets that not all
programs use cygwin1.dll. Cygwin is just the wrong place
were the problems of windows stupidity have to be fixed,
and so it does not fix them.
prev parent reply other threads:[~2007-03-08 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 4:16 [PATCH] Split sample update hook into post-receive hook Shawn O. Pearce
2007-03-08 8:26 ` Alex Riesen
2007-03-08 8:33 ` Shawn O. Pearce
2007-03-08 9:06 ` Junio C Hamano
2007-03-08 9:13 ` Shawn O. Pearce
2007-03-08 9:40 ` Sergey Vlasov
2007-03-10 8:29 ` Shawn O. Pearce
2007-03-08 9:57 ` Alex Riesen
2007-03-08 10:02 ` Shawn O. Pearce
2007-03-08 12:09 ` Alex Riesen [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=81b0412b0703080409u5ae64698tfa70a8ba2de65df@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=rael@zopyra.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).