Re: cvs to git migration - keywords
От | Dave Page |
---|---|
Тема | Re: cvs to git migration - keywords |
Дата | |
Msg-id | AANLkTimL7lZkJLxiT_GV0RGi7B3FkCqx1Oy5TTMUqUJJ@mail.gmail.com обсуждение исходный текст |
Ответ на | cvs to git migration - keywords (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: cvs to git migration - keywords
Re: cvs to git migration - keywords |
Список | pgsql-hackers |
On Wed, Jul 7, 2010 at 10:01 AM, Magnus Hagander <magnus@hagander.net> wrote: > 1) We can migrate the repository with the keywords, and then make one big > commit just after (or before, that doesn't make a difference) removing > them. In this case, backbranches and tags look exactly like they do > now, but it also means if you do "git diff" between old versions, the > keywords will show up there. > > 2) We can filter out that row during the conversion, so they look like > they never existed.That means that if you check out 7.4.3 or whatever > fro git, it will look like the keyword lines never existed. Since > they're in comments it shouldn''t affect functionality, but it does mean > that we are *not* keeping history unmodified. The advantage is that > "git diff" on and between old revision won't include the keyword > changes, of course. > > #1 is most likely the easiest one. +1 for #1. Changing history and the resulting possibility of becoming one's own grandfather always makes me nervous. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: