From: Roland Dreier <rolandd@cisco.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Peter Osterlund <petero2@telia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: What's up with the GIT archive on www.kernel.org?
Date: Sun, 11 Sep 2005 14:09:30 -0700 [thread overview]
Message-ID: <52irx7cnw5.fsf@cisco.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509111251150.3242@g5.osdl.org> (Linus Torvalds's message of "Sun, 11 Sep 2005 12:56:12 -0700 (PDT)")
Linus> You can try removing all the packs in your
Linus> .git/objects/packs directory. Everything _should_ still
Linus> work fine.
Does "everything" include someone doing
git clone rsync://rsync.kernel.org/pub/scm/linux/kernel/git/roland/whatever.git
How about http:// instead of rsync://?
In other words, is the git network transport smart enough to handle
the alternates path?
Or is the idea that everyone will clone your tree and then pull extra
stuff from other trees?
- R.
next prev parent reply other threads:[~2005-09-11 21:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 16:02 What's up with the GIT archive on www.kernel.org? Peter Osterlund
2005-09-11 16:12 ` Linus Torvalds
2005-09-11 18:57 ` Sam Ravnborg
2005-09-11 19:06 ` Linus Torvalds
2005-09-11 19:46 ` Sam Ravnborg
2005-09-11 19:56 ` Linus Torvalds
2005-09-11 21:09 ` Roland Dreier [this message]
2005-09-11 21:24 ` Linus Torvalds
2005-09-11 21:33 ` Linus Torvalds
2005-09-12 1:39 ` Junio C Hamano
2005-09-12 2:45 ` Dmitry Torokhov
2005-09-12 18:42 ` Ryan Anderson
2005-09-12 3:39 ` Linus Torvalds
2005-09-12 17:10 ` H. Peter Anvin
2005-09-12 18:22 ` Tony Luck
2005-09-12 18:37 ` Linus Torvalds
2005-09-11 22:12 ` Andrew Morton
2005-09-11 22:49 ` Alex Riesen
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=52irx7cnw5.fsf@cisco.com \
--to=rolandd@cisco.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--cc=sam@ravnborg.org \
--cc=torvalds@osdl.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