Re: cvs to git migration - keywords
От | Marko Kreen |
---|---|
Тема | Re: cvs to git migration - keywords |
Дата | |
Msg-id | AANLkTikTW4sqBU94pUGIZi_H1ckwIusoiWeLLSvb9i2P@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: cvs to git migration - keywords (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: cvs to git migration - keywords
|
Список | pgsql-hackers |
On 7/15/10, Andrew Dunstan <andrew@dunslane.net> wrote: > Marko Kreen wrote: > > On 7/7/10, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > > Robert Haas <robertmhaas@gmail.com> writes: > > > > So what happens right now using the existing git repository is that > > > > the $PostgeSQL$ tags are there, but they're unexpanded. They just > say > > > > $PostgreSQL$ rather than $PostgreSQL: tgl blah blah$. > > > > > > > > > Really? All of them? Seems like that would have taken some intentional > > > processing somewhere. > > > > > > > > > > AFAIK that's what CVS actually keeps in repo, it expands keywords > > when writing files out. > > > > > > > > No. It stores the expanded keyword. Just look in the ,v files in a CVS > mirror and you'll see them. Eh. I stand corrected - what it actually does is even more bizarre - it stores whatever is on the disk, but then expands on re-write. So: - r1.1 contains $Id$ in the repo. - r1.2 contains $Id: 1.1$ in the repo. and so on... -- marko
В списке pgsql-hackers по дате отправления: