Re: Managing multiple branches in git
От | David E. Wheeler |
---|---|
Тема | Re: Managing multiple branches in git |
Дата | |
Msg-id | 34ADC24F-FCD7-4880-AEFA-428C20DFF8AA@kineticode.com обсуждение исходный текст |
Ответ на | Re: Managing multiple branches in git (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Managing multiple branches in git
Re: Managing multiple branches in git |
Список | pgsql-hackers |
On Jun 2, 2009, at 9:03 AM, Tom Lane wrote: > "David E. Wheeler" <david@kineticode.com> writes: >> Yeah, with git, rather than cd'ing to another directory, you'd just >> do >> `git checkout rel8_3` and work from the same directory. > > That's what I'd gathered, and frankly it is not an acceptable answer. > Sure, the "checkout" operation is remarkably fast, but it does nothing > for derived files. What would really be involved here (if I wanted to > be sure of having a non-broken build) is > make maintainer-clean > git checkout rel8_3 > configure > make > which takes long enough that I'll have plenty of time to consider > how much I hate git. If there isn't a better way proposed, I'm > going to flip back to voting against this conversion. I need tools > that work for me not against me. Well, you can have as many clones of a repository as you like. You can keep one with master checked out, another with rel8_3, another with rel8_2, etc. You'd just have to write a script to keep them in sync (shouldn't be too difficult, each just as all the others as an origin -- or maybe you have one that's canonical on your system). Best, David
В списке pgsql-hackers по дате отправления: