Re: Managing multiple branches in git - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Managing multiple branches in git
Date
Msg-id E082748E-7ACC-4305-990D-6CC573E2B3C0@kineticode.com
Whole thread Raw
In response to Re: Managing multiple branches in git  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Managing multiple branches in git  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Jun 2, 2009, at 2:31 PM, Tom Lane wrote:

> It's a bit premature to speculate about alternate history tools when
> we haven't figured out what the repository is going to look like.
> Right
> at the moment I'm much more concerned about the question of supporting
> a checkout-per-branch workflow.  That's something I use pretty nearly
> every day, whereas looking at the history is maybe a once-a-week kind
> of need at most.

Perhaps there's a master repository that corresonds to CVS HEAD, and
then release branches are actually separate git repositories. This
way, those who need to maintain back branches can do so with each
individual repository (and maybe cherry-pick commits to get them to be
the same in each repo; I'm not sure), and everyone else can just use
the master repository (and do their normal local branching and merging
routine as they use it).

Not idea, but might provide some relief…

Best,

David

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Managing multiple branches in git
Next
From: Tom Lane
Date:
Subject: Re: Managing multiple branches in git