From: "Michel Dänzer" <michel@daenzer.net>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [ANN] Introducing new "test" branch in powerpc.git tree
Date: Sun, 08 Feb 2009 12:56:09 +0100 [thread overview]
Message-ID: <1234094169.5081.540.camel@thor.local> (raw)
In-Reply-To: <1233942156.5081.454.camel@thor.local>
On Fri, 2009-02-06 at 18:42 +0100, Michel D=C3=A4nzer wrote:
> On Thu, 2009-02-05 at 15:58 -0500, Josh Boyer wrote:
> > On Fri, Feb 06, 2009 at 07:56:22AM +1100, Benjamin Herrenschmidt wrote:
> > >
> > >> Which begs the question of what master is for. So far, it's just be=
en
> > >> a mirror of next from what I can tell. Maybe it should just track
> > >> Linus' tree?
> > >
> > >I've been wondering myself what to do with it ... I may just leave it =
to
> > >track linus indeed. Or maybe just delete it.
> >=20
> > I don't think you can delete it without hosing people who try to clone =
it.
>=20
> The branch to check out by git clone can be overridden via a special
> file in the .git directory in the shared repository. Unfortunately
> though, I don't remember what it's called...
According to Julien Cristau of the Debian X Strike Force (none of the
Git repos of which have a master branch), it should be .git/HEAD. Some
experiments of mine seem to confirm this.
--=20
Earthling Michel D=C3=A4nzer | http://www.vmware.c=
om
Libre software enthusiast | Debian, X and DRI developer
prev parent reply other threads:[~2009-02-08 11:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 4:01 [ANN] Introducing new "test" branch in powerpc.git tree Benjamin Herrenschmidt
2009-02-05 4:20 ` Grant Likely
2009-02-05 9:45 ` Wolfram Sang
2009-02-05 16:06 ` Grant Likely
2009-02-05 16:10 ` Wolfram Sang
2009-02-05 5:53 ` Kumar Gala
2009-02-05 7:02 ` Benjamin Herrenschmidt
2009-02-05 13:47 ` Josh Boyer
2009-02-05 20:56 ` Benjamin Herrenschmidt
2009-02-05 20:58 ` Josh Boyer
2009-02-06 17:42 ` Michel Dänzer
2009-02-08 11:56 ` Michel Dänzer [this message]
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=1234094169.5081.540.camel@thor.local \
--to=michel@daenzer.net \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.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).