From: Robert Haas <robertmhaas@gmail.com>
To: Greg Stark <stark@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Aidan Van Dyk <aidan@highrise.ca>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Markus Wanner <markus@bluegap.ch>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Thu, 28 May 2009 11:38:07 -0400
Message-ID: <603c8f070905280838s5bebb79bn37e4dc4a6c97daf7@mail.gmail.com> (raw)
In-Reply-To: <4136ffa0905280804i1653d716j7a39468fc56b5e5c@mail.gmail.com>
References: <10273.1243343651@sss.pgh.pa.us>
<20090527212240.GP15213@yugib.highrise.ca>
<603c8f070905271829i9458bdftcaed2dadb0a74583@mail.gmail.com>
<20090528020909.GQ15213@yugib.highrise.ca>
<603c8f070905271942ke9df2aah8648fe4d1228d43e@mail.gmail.com>
<20090528125944.GS15213@yugib.highrise.ca>
<603c8f070905280649m5d5fc458se54435dfe20cc7ca@mail.gmail.com>
<4A1E9D98.7030208@dunslane.net>
<8547.1243522369@sss.pgh.pa.us>
<4136ffa0905280804i1653d716j7a39468fc56b5e5c@mail.gmail.com>
On Thu, May 28, 2009 at 11:04 AM, Greg Stark <stark@enterprisedb.com> wrote:
> On Thu, May 28, 2009 at 3:52 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Andrew Dunstan <andrew@dunslane.net> writes:
>>> Robert Haas wrote:
>>>> That would suck for me. I use git log a lot to see how things have
>>>> changed over time.
>>
>>> Indeed. Losing the history is not an acceptable option.
>>
>> I think the same. If git is not able to maintain our project history
>> then it is not mature enough to be considered as our official VCS.
>> This is not a negotiable requirement.
>
> I think the idea is that you could choose, for example, the level of
> granularity you want to keep. That could be interesting in the future
> -- someone who submitted a patch (or anyone who was working in that
> area) might want to keep all their intermediate commits and not just
> the one big commit for the whole feature.
I don't think that was the idea - Aidan floated the idea of just
checking the current version of each branch into git, rather than
importing the full history from CVS (and letting indivdual cloners fix
their own history if they were so inclined). I think that's a
non-starter.
I'm still not sure who is going to take responsibility for fixing the
git tree we have now. I don't think it's going to work for us to
leave it broken until we're ready to do "the cutover", and then do one
monolithic move. If the tools we're using to do the import now have
broken our tree, then we need to fix it, and them. Ideally I'd like
to get a bi-directional conversion working, so that committers could
commit via either CVS or GIT during the transition, but I'm not sure
whether that's feasible.
...Robert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: robertmhaas@gmail.com, stark@enterprisedb.com, tgl@sss.pgh.pa.us, andrew@dunslane.net, aidan@highrise.ca, heikki.linnakangas@enterprisedb.com, magnus@hagander.net, markus@bluegap.ch
Subject: Re: PostgreSQL Developer meeting minutes up
In-Reply-To: <603c8f070905280838s5bebb79bn37e4dc4a6c97daf7@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox