Re: Hacking on PostgreSQL via GIT
От | Tom Lane |
---|---|
Тема | Re: Hacking on PostgreSQL via GIT |
Дата | |
Msg-id | 21068.1176874394@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Hacking on PostgreSQL via GIT (Martin Langhoff <martin@catalyst.net.nz>) |
Ответы |
Re: Hacking on PostgreSQL via GIT
Re: Hacking on PostgreSQL via GIT Re: Hacking on PostgreSQL via GIT |
Список | pgsql-hackers |
Martin Langhoff <martin@catalyst.net.nz> writes: > Aidan Van Dyk wrote: >> And remember the warning I gave that my conversion is *not* a direct CVS >> import - I intentionally *unexpand* all Keywords before stuffing them >> into GIT so that merging and branching can ignore all the Keyword >> conflicts... > My import is unexpanding those as well to support rebasing and merging > better. Um ... why do either of you feel there's an issue there? We switched over to $PostgreSQL$ a few years ago specifically to avoid creating merge problems for downstream repositories. If there are any other keyword expansions left in the source text I'd vote to remove them. If you have a problem with $PostgreSQL$, why? regards, tom lane
В списке pgsql-hackers по дате отправления: