public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sitaram Chamarty <sitaramc@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: problem with git.kernel.org
Date: Mon, 15 Dec 2008 16:07:18 +0000 (UTC)	[thread overview]
Message-ID: <gi5vbm$tts$1@ger.gmane.org> (raw)
In-Reply-To: 49465862.9090400@s5r6.in-berlin.de

On 2008-12-15, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:

> Chris, you should enable fetching over http by
> $ cd /pub/scm/linux/kernel/git/mason/btrfs-unstable-standalone.git
> $ cp -p hooks/post-update.sample hooks/post-update

I notice that the .git/hooks/post-update still calls it
"git-update-server-info".  Shouldn't that be "git
update-server-info"?

[my git is 1.6.0.2, but even on a checked out though not
compiled-and-installed 1.6.0.4 it is the same]

> Cloning a full kernel repo over http may be too unreliable, but cloning
> a smaller repo like the btrfs standalone repo should work acceptably
> over http.

Maybe git bundle can help.  Perhaps there can be some
documented way of creating a HTTP-downloadable bundle from
the current "master" in any web-accessible git to make
things really easy for first time downloaders, maybe updated
only once in a month or so.  Anyone having trouble doing a
clone would get this, fetch it in, set up remote/origin, and
then do a normal pull...


  reply	other threads:[~2008-12-15 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 12:42 problem with git.kernel.org devzero
2008-12-15 13:15 ` Stefan Richter
2008-12-15 16:07   ` Sitaram Chamarty [this message]
2008-12-16 12:10     ` Stefan Richter
2008-12-15 20:54   ` Chris Mason
  -- strict thread matches above, loose matches on Subject: below --
2008-12-15  9:22 devzero
2008-12-15 10:22 ` Stefan Richter

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='gi5vbm$tts$1@ger.gmane.org' \
    --to=sitaramc@gmail.com \
    --cc=linux-kernel@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