Date: Thu, 28 May 2009 08:59:44 -0400
From: Aidan Van Dyk <aidan@highrise.ca>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>,
	Magnus Hagander <magnus@hagander.net>, Markus Wanner <markus@bluegap.ch>,
	Andrew Dunstan <andrew@dunslane.net>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
Message-ID: <20090528125944.GS15213@yugib.highrise.ca>
References: <10273.1243343651@sss.pgh.pa.us> <4A1BFF70.4000506@dunslane.net>
	<20090526144812.GC15213@yugib.highrise.ca>
	<20090527121532.83276r2btyqp716s@mail.bluegap.ch>
	<4A1D1E64.6030908@hagander.net> <4A1D2290.7060907@enterprisedb.com>
	<20090527212240.GP15213@yugib.highrise.ca>
	<603c8f070905271829i9458bdftcaed2dadb0a74583@mail.gmail.com>
	<20090528020909.GQ15213@yugib.highrise.ca>
	<603c8f070905271942ke9df2aah8648fe4d1228d43e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="WfjJTYUClXDJCnRl"
Content-Disposition: inline
In-Reply-To: <603c8f070905271942ke9df2aah8648fe4d1228d43e@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)


--WfjJTYUClXDJCnRl
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Robert Haas <robertmhaas@gmail.com> [090527 22:43]:
> On Wed, May 27, 2009 at 10:09 PM, Aidan Van Dyk <aidan@highrise.ca> wrote:
> > * Robert Haas <robertmhaas@gmail.com> [090527 21:30]:
> >
> >> > And actually looking at the history of the gpo repo, the branches ar=
e all
> >> > messed up with "merges" and stuff that I'm not sure where they are c=
oming
> >> > from... =A08.2, 8.3, and master(HEAD) are all the same as my gpo rep=
o, but the
> >> > back branchs are very bad...
> >>
> >> This is really quite horrible. =A0What is the best way forward here?
> >
> > That depends entirely on what the project wants.
>=20
> I can't speak for anyone else, but what I want is for the git tree on
> git.postgresql.org to match CVS.

Well, sure, but I think the "way forward" part implied recognition that
the current tree at git.postgresql.org *doesn't* match CVS very closely
(for back branches), and that people currently rely on it and use it.

So, again, the answer to the question really does depend on what the
"canonical" VCS of the project is.  As of now, it's *still* CVS, and
those using either git repo can still develop and submit patches to CVS
easily.

When the project switches, there will probably need to be a more
canonical conversion, with one of the tools that doesn't support
incremental imports, and then people will have to adjust their current
repo with any of rebase/graft/filter-branch to adjust their work
history onto the "official" tree...

All that based on the assumption that when the project switches to git,
they actually want all the CVS history in their official tree.  Its
certainly not necessary, and possibly not even desirable...  PostgreSQL
could just as easily to a "linus" style switch when they switch to git,
and just "import" the latest release in each branch as the starting
point for each branch.  The git repository will have no history, and
people can choose which history they want to graft in...  CVSROOT can be
made available as a historical download.

a.

--=20
Aidan Van Dyk                                             Create like a god,
aidan@highrise.ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

--WfjJTYUClXDJCnRl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFKHorAuVxNPsxNPScRAgnuAJ9M5eUo+zVxNi/jTAJQNjPuIf/1IwCfeO1C
/PJjsI6voGai1KGzgJCJbsc=
=qg6s
-----END PGP SIGNATURE-----

--WfjJTYUClXDJCnRl--