From: Sergey Vlasov <vsu@altlinux.ru>
To: "Shawn O. Pearce" <spearce@spearce.org>
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: Thu, 8 Mar 2007 12:40:24 +0300 [thread overview]
Message-ID: <20070308124024.d20e29c9.vsu@altlinux.ru> (raw)
In-Reply-To: <20070308091313.GC30289@spearce.org>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On Thu, 8 Mar 2007 04:13:13 -0500 Shawn O. Pearce wrote:
> Junio C Hamano <junkio@cox.net> wrote:
[...]
> > But this is only true if you want to make it really nice. I
> > personally feel that nobody would scream if pushing 1300 refs at
> > once (4K pages and MAX_ARG_PAGES at 32 would give 128K for
> > **argv and its strings, and one ref's worth of data is two
> > 40-digit hex plus refname, roughly 100-byte per ref) is not
> > supported and always failed.
>
> 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?
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-08 9:41 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 [this message]
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
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=20070308124024.d20e29c9.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=raa.lkml@gmail.com \
--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 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.