From: Junio C Hamano <junkio@cox.net>
To: Nick Hengeveld <nickh@reactrix.com>
Cc: git@vger.kernel.org
Subject: Re: HTTP questions
Date: Thu, 01 Jun 2006 23:38:57 -0700 [thread overview]
Message-ID: <7vhd34dptq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060601232437.GD12261@reactrix.com> (Nick Hengeveld's message of "Thu, 1 Jun 2006 16:24:37 -0700")
Nick Hengeveld <nickh@reactrix.com> writes:
> - "git push" seems to pass --thin by default to http-push, which
> subsequently barfs because that's not a valid http-push option.
> Should it be? Should it be silently ignored? Should git-push not
> default to --thin when pushing with HTTP transport?
The way I understand http-push works is that it does not use
packed transfer, so I presume even if we give --thin as a hint
it cannot even take advantage of it. Probably we should stop
passing --thin to http transport (git native one uses it as a
cue that it can generate baseless deltas in the resulting pack).
> - when I clone, http-fetch outputs a whole bunch of
> "error: Could not read ..." messages - is that expected?
The clone over http seems to be severely broken in "next" right
now. The one in "master" seems to be OK. bisecting suggests
the breakage is coming from the tree parser rewrite.
bisect points at 136f2e548a34f1f504b0f062f87ddf33e8d6e83b.
next prev parent reply other threads:[~2006-06-02 6:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 23:24 HTTP questions Nick Hengeveld
2006-06-02 6:38 ` Junio C Hamano [this message]
2006-06-02 17:38 ` http-fetch troubles Junio C Hamano
2006-06-02 22:15 ` Junio C Hamano
2006-06-02 22:34 ` Linus Torvalds
2006-06-03 1:13 ` Becky Bruce
2006-06-03 1:24 ` Junio C Hamano
2006-06-03 2:26 ` Linus Torvalds
2006-06-03 7:58 ` Junio C Hamano
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=7vhd34dptq.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=nickh@reactrix.com \
/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).