Re: Git conversion status

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Git conversion status
Дата
Msg-id 1663.1285188929@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Git conversion status  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Git conversion status  (Andrew Dunstan <andrew@dunslane.net>)
Re: Git conversion status  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Sep 22, 2010 at 4:04 PM, Alvaro Herrera
> <alvherre@commandprompt.com> wrote:
>> As far as I can see, I need to go to the master clone, run a checkout
>> and pull on each branch, and *then* a pull on the local clone updates to
>> the latest head on that branch. �It is not enough to pull when the
>> master branch is checked out.

> Ah, crap.  You're right.  Sucktastic.

As far as I can tell so far, the multiple-workdir setup dominates all
the others in terms of minimizing the amount of "git pull" monkeywork.
You still have to remember to do that (or some equivalent) in each
workdir to update that workdir, but that's no worse than with multiple
CVS checkout directories.  And the amount of network overhead is a LOT
less than with multiple CVS checkouts.

(In particular, I'm avoiding Andrew's preferred alternative with the
extra local repository; I don't want an asynchronous buffer between me
and the real repository.  I guess if you had a really bad network
connection it could be useful, but considering how much better this is
than CVS already, I won't miss whatever savings that might offer.)
        regards, tom lane


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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Git conversion status
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Git conversion status