From: merlyn@stonehenge.com (Randal L. Schwartz)
To: git@vger.kernel.org
Subject: Re: maybe breakage with latest git-pull and http protocol
Date: 14 Oct 2005 03:58:27 -0700 [thread overview]
Message-ID: <864q7kqsa4.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <867jciz18w.fsf@blue.stonehenge.com>
>>>>> "Randal" == Randal L Schwartz <merlyn@stonehenge.com> writes:
Randal> I updated git to d06b689a933f6d2130f8afdf1ac0ddb83eeb59ab,
Randal> then compiled and installed.
Randal> When I went to "git-pull" on my cogito archive (which I had edited
Randal> to use HTTP instead of RSYNC), I got into trouble. Unfortunately,
Randal> I changed it to rsync to force cogito into a sane state before
Randal> I realized that this would be a good bug report. :)
Randal> This is perhaps just a heads-up that the recent git-pull might be
Randal> broken with respect to http updates.
Even after updating git this morning, git-pull still seems to be broken
with respect to http://www.kernel.org/.
Is http pulling broken for good now? Or is someone looking at this?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2005-10-14 10:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 0:53 maybe breakage with latest git-pull and http protocol Randal L. Schwartz
2005-10-13 5:50 ` Junio C Hamano
2005-10-14 10:58 ` Randal L. Schwartz [this message]
2005-10-14 15:42 ` Junio C Hamano
2005-10-14 16:18 ` Randal L. Schwartz
2005-10-14 19:56 ` Daniel Barkalow
2005-10-15 13:03 ` Randal L. Schwartz
2005-10-15 16:04 ` Junio C Hamano
2005-10-15 16:22 ` Junio C Hamano
2005-10-15 19:41 ` Daniel Barkalow
2005-10-15 21:56 ` Nick Hengeveld
2005-10-15 21:21 ` Nick Hengeveld
2005-10-15 16:37 ` Junio C Hamano
2005-10-15 17:13 ` Junio C Hamano
2005-10-15 21:57 ` Nick Hengeveld
2005-10-15 22:04 ` Randal L. Schwartz
2005-10-20 17:43 ` Nick Hengeveld
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=864q7kqsa4.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.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).