Re: cvs to git migration - keywords

From: Marko Kreen <markokr(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: cvs to git migration - keywords
Date: 2010-07-15 17:48:59
Message-ID: AANLkTikTW4sqBU94pUGIZi_H1ckwIusoiWeLLSvb9i2P@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/15/10, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Marko Kreen wrote:
> > On 7/7/10, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > > Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc G. Fournier 2010-07-15 17:54:27 Re: SHOW TABLES
Previous Message Robert Haas 2010-07-15 17:47:31 Re: reducing NUMERIC size for 9.1