| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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-07 18:31:35 |
| Message-ID: | 4C34C807.5010104@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> 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$. I'm all in
> favor of removing them, but it would be nice if we could avoid
> cluttering the old changesets with useless changes to the keyword
> expansions.
>
>
>
Personally I favor leaving the expanded keywords in what we import, so
that there's an exact mapping between what's in the final CVS repo and
what's in the inital git repo, and then removing them entirely. I don't
see that having old keyword expansions in the historical changesets is a
bid deal. Nobody is going to base patches on them (I hope).
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-07-07 18:34:53 | Re: cvs to git migration - keywords |
| Previous Message | Alvaro Herrera | 2010-07-07 17:29:04 | Re: t_self as system column |