Skip site navigation (1) Skip section navigation (2)

Re: git: uh-oh

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Haggerty <mhagger(at)alum(dot)mit(dot)edu>, Max Bowsher <maxb(at)f2s(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: git: uh-oh
Date: 2010-08-31 11:41:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mon, Aug 30, 2010 at 05:03, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Aug 25, 2010 at 2:39 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Wed, Aug 25, 2010 at 1:27 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>>> The fact that the file was "modified" twice after being removed at rev
>>>> 2.88 seems really wacko.  Are you sure that's not contributing to what
>>>> we're seeing here?
>>> Yeah, that was discussed in the earlier git-conversion thread that I
>>> pointed to.  We never did figure out how that happened, though I
>>> speculated it might have been due to weirdness in Vadim's local
>>> checkout.
>>> Is it possible to just delete those two revisions from the CVS
>>> repository, and if so would it help?  We certainly don't need 'em.
>> cvs admin -o ?
> Magnus, is this something that you can try?  Prune those could of
> wonky revisions after the delete and before the re-add prior to
> running the conversion, and see how that comes out?

Yes, definitely.

Do we have list of exactly which revisions it is, or a good way to
find it? Other than random browsing of the history? :-)

 Magnus Hagander

In response to


pgsql-hackers by date

Next:From: Pavel StehuleDate: 2010-08-31 11:47:34
Subject: Re: thousand unrelated data files in pg_default tablespace
Previous:From: Magnus HaganderDate: 2010-08-31 11:21:38
Subject: Re: Git conversion progress report and call for testing assistance

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group