Re: Managing multiple branches in git

Поиск
Список
Период
Сортировка
Искать
От
David E. Wheeler
Тема
Re: Managing multiple branches in git
Дата
Msg-id
E082748E-7ACC-4305-990D-6CC573E2B3C0@kineticode.com
Ответ на
Список
Дерево обсуждения
Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Aidan Van Dyk <aidan@highrise.ca>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Greg Stark <greg.stark@enterprisedb.com>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Aidan Van Dyk <aidan@highrise.ca>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Aidan Van Dyk <aidan@highrise.ca>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Greg Stark <greg.stark@enterprisedb.com>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Bruce Momjian <bruce@momjian.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Stephen Frost <sfrost@snowman.net>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Stephen Frost <sfrost@snowman.net>
Re: Managing multiple branches in git "Markus Wanner" <markus@bluegap.ch>
Re: Managing multiple branches in git Greg Stark <stark@enterprisedb.com>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "Joshua D. Drake" <jd@commandprompt.com>
Re: Managing multiple branches in git Aidan Van Dyk <aidan@highrise.ca>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Dave Page <dpage@pgadmin.org>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Magnus Hagander <magnus@hagander.net>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "Joshua D. Drake" <jd@commandprompt.com>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Dave Page <dpage@pgadmin.org>
Re: Managing multiple branches in git Dave Page <dpage@pgadmin.org>
Re: Managing multiple branches in git Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Peter Eisentraut <peter_e@gmx.net>
Re: Managing multiple branches in git Greg Smith <gsmith@gregsmith.com>
Re: Managing multiple branches in git "Greg Sabino Mullane" <greg@turnstep.com>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Marko Kreen <markokr@gmail.com>
Re: Managing multiple branches in git Florian Weimer <fweimer@bfk.de>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Marko Kreen <markokr@gmail.com>
Re: Managing multiple branches in git Dave Page <dpage@pgadmin.org>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git "Markus Wanner" <markus@bluegap.ch>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git "Markus Wanner" <markus@bluegap.ch>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Aidan Van Dyk <aidan@highrise.ca>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Marko Kreen <markokr@gmail.com>
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 по дате отправления
От: Robert Haas
Дата:
От: Tom Lane
Дата:
FAQ