From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: [PATCH] Re: git-http-pull broken in latest git
Date: Thu, 11 Aug 2005 19:01:46 -0700 [thread overview]
Message-ID: <7vzmrnc3qt.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0508111929010.12816@iabervon.org> (Daniel Barkalow's message of "Thu, 11 Aug 2005 19:38:09 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> It should work anyway,...
That is true. Please forget about the "recommendation" to slurp
packs and not falling back on commit walker.
Thanks for the patch.
next prev parent reply other threads:[~2005-08-12 2:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 16:06 cg-clone http://www.kernel.org/pub/scm/git/git.git fails Dirk Behme
2005-08-11 22:33 ` git-http-pull broken in latest git Petr Baudis
2005-08-11 23:21 ` Junio C Hamano
2005-08-11 23:38 ` [PATCH] " Daniel Barkalow
2005-08-12 2:01 ` Junio C Hamano [this message]
2005-08-12 2:12 ` Daniel Barkalow
2005-08-11 23:57 ` Junio C Hamano
2005-08-12 2:45 ` Petr Baudis
2005-08-12 3:17 ` [PATCH] " Daniel Barkalow
2005-08-12 5:20 ` Junio C Hamano
2005-08-12 15:37 ` Daniel Barkalow
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=7vzmrnc3qt.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).