cvs to git migration - keywords
in [PgSql]
|
From: Marko Kreen on 15 Jul 2010 13:48 On 7/15/10, Andrew Dunstan <andrew(a)dunslane.net> wrote: > Marko Kreen wrote: > > On 7/7/10, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: > > > Robert Haas <robertmhaas(a)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 -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Aidan Van Dyk on 15 Jul 2010 13:56 * Marko Kreen <markokr(a)gmail.com> [100715 13:49]: > 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... It's actually slightly *worse* than that... The repository r$N contains what was in the commiters $N-1 *checked out* copy when he commits. So what's in the ,v file has *nothing* to do with reality, except by chance it's $n-1 because that's what was last checkout/updated most of the time.. -- Aidan Van Dyk Create like a god, aidan(a)highrise.ca command like a king, http://www.highrise.ca/ work like a slave.
From: Aidan Van Dyk on 15 Jul 2010 14:04 * Aidan Van Dyk <aidan(a)highrise.ca> [100715 13:56]: > * Marko Kreen <markokr(a)gmail.com> [100715 13:49]: > > > 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... > > It's actually slightly *worse* than that... The repository r$N contains > what was in the commiters $N-1 *checked out* copy when he commits. So > what's in the ,v file has *nothing* to do with reality, except by chance > it's $n-1 because that's what was last checkout/updated most of the > time.. And as a demo of what you can see in a project where some of my machines have -kk in .cvsrc, and others don't: [aidan(a)d1 faxd]$ grep '\$Id' faxQueueApp.c++,v |less /* $Id$ */ /* $Id: faxQueueApp.c++,v 1.115 2007/09/17 19:34:41 aidan Exp $ */ /* $Id$ */ /* $Id: faxQueueApp.c++,v 1.112 2007/07/23 21:04:09 aidan Exp $ */ /* $Id$ */ /* $Id: faxQueueApp.c++,v 1.113.2.2 2007/09/07 18:39:26 aidan Exp $ /* $Id$ */ /* $Id$ */ /* $Id: faxQueueApp.c++,v 1.111 2007/06/05 18:51:16 aidan Exp $ */ /* $Id$ */ a. -- Aidan Van Dyk Create like a god, aidan(a)highrise.ca command like a king, http://www.highrise.ca/ work like a slave.
First
|
Prev
|
Pages: 1 2 3 4 Prev: [HACKERS] cvs to git migration - keywords Next: Python Interface Hacking |