All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Sergey Vlasov <vsu@altlinux.ru>
Cc: Junio C Hamano <junkio@cox.net>, Alex Riesen <raa.lkml@gmail.com>,
	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: Sat, 10 Mar 2007 03:29:23 -0500	[thread overview]
Message-ID: <20070310082923.GA4092@spearce.org> (raw)
In-Reply-To: <20070308124024.d20e29c9.vsu@altlinux.ru>

Sergey Vlasov <vsu@altlinux.ru> wrote:
> On Thu, 8 Mar 2007 04:13:13 -0500 Shawn O. Pearce wrote:
> > Agree completely.  I'm not too worried about it.  1300 ref push is
> > just not going to really occur in practice; that is just insane.
> > 30 refs, maybe.
> 
> It is not completely insane - e.g., the current klibc repository
> already contains 338 tags.  Being unable to use "git push --tags" to
> an initially empty repository does not look good.
> 
> So could you please switch to passing refs through stdin while we
> still can do it without breaking public interfaces?

Fixed with my latest 8 patch series.  We now pass the ref data
to the new {pre,post}-receive hooks by stdin, rather than as
command line arguments.

Thanks for the reality check.  ;-)

-- 
Shawn.

  reply	other threads:[~2007-03-10  8:30 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 [this message]
2007-03-08  9:57       ` Alex Riesen
2007-03-08 10:02         ` Shawn O. Pearce
2007-03-08 12:09           ` Alex Riesen

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=20070310082923.GA4092@spearce.org \
    --to=spearce@spearce.org \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=raa.lkml@gmail.com \
    --cc=rael@zopyra.com \
    --cc=vsu@altlinux.ru \
    /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.