This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: onwards to git
- From: Roland McGrath <roland at redhat dot com>
- To: "Carlos O'Donell" <carlos at systemhalted dot org>
- Cc: Jim Meyering <jim at meyering dot net>, "Joseph S. Myers" <joseph at codesourcery dot com>, libc-ports at sourceware dot org
- Date: Fri, 1 May 2009 13:14:41 -0700 (PDT)
- Subject: Re: onwards to git
- References: <49F89C2D.5060702@redhat.com> <Pine.LNX.4.64.0904292008041.31467@digraph.polyomino.org.uk> <20090429203933.08694FC3BF@magilla.sf.frob.com> <87hc07dt5x.fsf@meyering.net> <20090430195521.B8C59FC3BF@magilla.sf.frob.com> <119aab440905010655o78fd98f2oc819a266f97e5c0d@mail.gmail.com>
> I'm working on the website update and I have some questions...
This is slightly premature, in that we have not actually established the
detailed conventions for the git repository.
> Q: How do I checkout the glibc-2_9-branch from git?
>
> A: Checkout the sources from the glibc-2_9 tag into a local branch
> named glibc-2_9-branch
> git checkout -b glibc-2_9-branch glibc-2_9
The only branches/tags today are the cvs/* ones (e.g. cvs/glibc-2_9-branch).
Those branch names will not be part of any recommended procedure.
We can start hashing out the conventions for glibc-ports.git now.
But, we would like to harmonize those with the glibc.git conventions
for the most part. Those conventions will be hashed out on libc-hacker
and/or libc-alpha rather than here.
For right now, you can write draft web pages with instructions and examples
that say <placeholder:branch-name-here> (or whatever you like). Later only
the names will be changed to protect the innocent.
Thanks,
Roland