Re: Managing multiple branches in git

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Managing multiple branches in git
Дата
Msg-id 18188.1243974746@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Managing multiple branches in git  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Managing multiple branches in git  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> I wonder whether it would help with this problem if we had a way to
> locate the build products outside the tree, and maybe fix things up so
> that you can make the build products go to a different location
> depending on which branch you're on.

I'm beginning to seriously consider the idea that the git repository
should think each branch is a separate directory subtree --- ie,
completely abandon the notion that git is worth anything at all for
managing multi-branch patches.  If we have HEAD, REL8_3, etc as
separate subtrees then we can easily have a single commit touching
multiple branches in whatever way we want.

The arguments that were put forward for switching to git all had to do
with managing patches against HEAD.  AFAIK hardly anyone but the core
committers deals with back-patching at all, and so a structure like this
isn't going to affect anyone else --- you'd just ignore the back-branch
directory subtrees in your checkout.
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Mark Mielke
Дата:
Сообщение: Re: Managing multiple branches in git
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Locks on temp table and PREPARE