From: Russell King <rmk@arm.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc64-dev@ozlabs.org, Git Mailing List <git@vger.kernel.org>
Subject: Re: please pull ppc64-2.6.git
Date: Mon, 29 Aug 2005 18:45:10 +0100 [thread overview]
Message-ID: <20050829184510.A20605@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0508291006440.3243@g5.osdl.org>; from torvalds@osdl.org on Mon, Aug 29, 2005 at 10:32:09AM -0700
On Mon, Aug 29, 2005 at 10:32:09AM -0700, Linus Torvalds wrote:
> On Mon, 29 Aug 2005, Paul Mackerras wrote:
> > Please do a pull from:
> >
> > rsync://rsync.kernel.org/pub/scm/linux/kernel/git/paulus/ppc64-2.6.git
>
> Gaah.
>
> This is not a valid git repository.
>
> Guys, if you do partially populated repositories, _please_ make sure that
> you still make it a valid git repository. These days you can trivially do
> so by doing a
>
> echo /pub/scm/linux/kernel/git/torvalds/linux-2.6/objects > objects/info/alternates
>
> or similar. That also makes gitweb able to show diffs etc, something it
> can't do for a broken partial repository.
Is the expected filesystem layout documented somewhere online (_external_
to the source code) ?
The reason I stress external to the code is that some of us do not track
git developments. (Except via the ctrl-d method in our mail readers.)
Alternatively, when changes occur to the repostory format, please can
they be marked with some obvious subject so that folk know when things
are going to break?
--
Russell King
next prev parent reply other threads:[~2005-08-29 17:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17170.25803.413408.44080@cargo.ozlabs.ibm.com>
2005-08-29 17:32 ` please pull ppc64-2.6.git Linus Torvalds
2005-08-29 17:45 ` Russell King [this message]
2005-08-29 18:02 ` Linus Torvalds
2005-08-29 18:20 ` Russell King
2005-09-02 0:20 ` Junio C Hamano
2005-08-29 23:31 ` Paul Mackerras
2005-08-30 0:20 ` Linus Torvalds
2005-08-30 21:40 ` Christian Meder
2005-08-30 22:25 ` Junio C Hamano
2005-08-31 13:08 ` Sergey Vlasov
2005-08-31 18:39 ` 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=20050829184510.A20605@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=git@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).