From: Nick Hengeveld <nickh@reactrix.com>
To: git@vger.kernel.org
Subject: HTTP questions
Date: Thu, 1 Jun 2006 16:24:37 -0700 [thread overview]
Message-ID: <20060601232437.GD12261@reactrix.com> (raw)
While testing recent http-fetch changes with a current checkout of next,
I noticed a couple of things:
- "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?
- when I clone, http-fetch outputs a whole bunch of
"error: Could not read ..." messages - is that expected?
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next reply other threads:[~2006-06-01 23:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 23:24 Nick Hengeveld [this message]
2006-06-02 6:38 ` HTTP questions Junio C Hamano
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=20060601232437.GD12261@reactrix.com \
--to=nickh@reactrix.com \
--cc=git@vger.kernel.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 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).