From: Jonathan Nieder <jrnieder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Fredrik Gustafsson <iveqy@iveqy.com>,
Stefan Beller <stefanbeller@googlemail.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: getting git from kernel.org is failing
Date: Tue, 23 Jul 2013 13:40:05 -0700 [thread overview]
Message-ID: <20130723204005.GF14690@google.com> (raw)
In-Reply-To: <20130723202127.GA2051@sigill.intra.peff.net>
Jeff King wrote:
> then smart HTTP works fine. I wonder if there is a problem in the cgit
> setup on kernel.org (or if it was even intended that you could fetch
> from the cgit URL at all; the cgit page shows the clone URLs in
> /pub/scm/git).
I didn't think cgit URLs were meant to be clonable, but since
ls-remote works on them, it seems I thought wrong. :) Odd.
Thanks,
Jonathan
next prev parent reply other threads:[~2013-07-23 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 19:41 getting git from kernel.org is failing Stefan Beller
2013-07-23 20:06 ` Fredrik Gustafsson
2013-07-23 20:21 ` Jeff King
2013-07-23 20:40 ` Jonathan Nieder [this message]
2013-07-23 21:06 ` John Keeping
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=20130723204005.GF14690@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.com \
--cc=peff@peff.net \
--cc=stefanbeller@googlemail.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).