From: Andy Whitcroft <apw@shadowen.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: send-pack: limit on negative references
Date: Tue, 05 Sep 2006 22:32:01 +0100 [thread overview]
Message-ID: <44FDECD1.2090909@shadowen.org> (raw)
In-Reply-To: <7vwt8igu4u.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Andy Whitcroft <apw@shadowen.org> writes:
>
>> I've been having trouble with git push apparently resending the entire
>> commit trace for the branch each and every time I push; even with short
>> branch names. This seems to be related to the changes made to handle
>> the case where the remote end has a large number of branches (>900).
>
> I think the right fix is to do one or both of the following, and
> lift that 900 cut-off entirely.
>
> One is to teach rev-list to read the information it is taking
> from the command line instead from its standard input.
>
> Another is to teach pack-object the same trick on top of my
> patch last night. This has an added benefit that we save one
> pipe+fork+exec there.
>
> These are essentially suggestions from Linus made twice
> separately in the past, so they must be on the right track ;-).
>
> If nobody does, I would do it myself, but the list is welcome to
> beat me to it. Especially, the former (giving --stdin option to
> rev-list) should be trivial.
Ok, I'll have a go at this one. As you say it looks pretty simple to
reuse the command line revision parser on an incoming stream.
-apw
next prev parent reply other threads:[~2006-09-05 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 12:45 send-pack: limit on negative references Andy Whitcroft
2006-09-05 16:23 ` Junio C Hamano
2006-09-05 21:32 ` Andy Whitcroft [this message]
2006-09-05 21:51 ` [PATCH 1/2] rev list add option accepting revision constraints on standard input Andy Whitcroft
2006-09-05 22:10 ` Junio C Hamano
2006-09-06 1:01 ` Andy Whitcroft
2006-09-06 4:46 ` Junio C Hamano
2006-09-05 21:52 ` [PATCH 2/2] send pack switch to using git rev list stdin Andy Whitcroft
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=44FDECD1.2090909@shadowen.org \
--to=apw@shadowen.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.