This is the mail archive of the libc-ports@sources.redhat.com mailing list for the libc-ports project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: onwards to git

From: "Carlos O'Donell" <carlos at systemhalted dot org>
To: Thomas Schwinge <tschwinge at gnu dot org>
Cc: Roland McGrath <roland at redhat dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, libc-ports at sourceware dot org, Jim Meyering <jim at meyering dot net>
Date: Thu, 30 Apr 2009 10:47:43 -0400
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> <20090430084652.GE25844@fencepost.gnu.org>

On Thu, Apr 30, 2009 at 4:46 AM, Thomas Schwinge <tschwinge@gnu.org> wrote:
> Just a suggestion from someone who isn't actively using the ports
> repository: why not have separate Git repositories for each individual
> port, and base these repositories on the [glibc]/master branch? ?Doing
> so, the ports maintainers could periodically merge in [glibc]/master into
> their ports' branches (which may either be in a separate repository or in
> the main glibc repository), and it would also automatically be documented
> which port is maintained, which was the last version of [glibc]/master
> this port was tested with.

I think this would be a great idea.

Cheers,
Carlos.

Follow-Ups:
- Re: onwards to git
  - From: Daniel Jacobowitz

References:
- Re: onwards to git
  - From: Joseph S. Myers
- Re: onwards to git
  - From: Roland McGrath
- Re: onwards to git
  - From: Thomas Schwinge

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]