| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Report: removing the inconsistencies in our CVS->git conversion |
| Date: | 2010-09-17 21:35:27 |
| Message-ID: | AANLkTikUafNdxsc+kxw48Q5Xaa58fHuZQ6ud2CoDQzVO@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
On Fri, Sep 17, 2010 at 23:21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Actually, the simplest way to handle this might be to just delete all
> five of those tags during the conversion, and then I'll put them back
> in the right places later when I add the other old-release tags.
> That way we won't have any tags getting moved after the repository is
> published. (Or am I wrong about that being something to avoid? But
> in any case we want to gc the manufactured commits for Release_2_0_0
> and Release_2_0.)
As long as nobody has cloned the repository, it's not a problem moving
them. But it *is* something you should generally avoid, so let's do
that :-)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph Adams | 2010-09-17 21:45:35 | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |
| Previous Message | Magnus Hagander | 2010-09-17 21:34:28 | Re: Report: removing the inconsistencies in our CVS->git conversion |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2010-09-17 22:00:49 | Re: error on http://wiki.postgresql.org/wiki/Lock_Monitoring |
| Previous Message | Magnus Hagander | 2010-09-17 21:34:28 | Re: Report: removing the inconsistencies in our CVS->git conversion |