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

Re: Problem in GIT mirror (was Re: pgsql: Fix all theserver-side SIGQUIT handlers ...)

From: David Fetter <david(at)fetter(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>,Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-www(at)postgresql(dot)org,Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: Problem in GIT mirror (was Re: pgsql: Fix all theserver-side SIGQUIT handlers ...)
Date: 2009-05-18 16:29:35
Message-ID: 20090518162935.GA4860@fetter.org (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-www
On Mon, May 18, 2009 at 11:29:00AM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Tom Lane wrote:
> >> We should assume this will be less buggy?
> 
> > Well, actually yes -- the git-to-cvs mechanism is integrated in Git,
> > whereas the cvs-to-git mirror is a rather unsupported hack.
> > http://www.kernel.org/pub/software/scm/git/docs/git-cvsserver.html
> 
> I quote from that page:
> 
> >>> It is highly functional. However, not all methods are
> >>> implemented, and for those methods that are implemented, not all
> >>> switches are implemented. 
> 
> >>> Testing has been done using both the CLI CVS client, and the
> >>> Eclipse CVS plugin. Most functionality works fine with both of
> >>> these clients. 
> 
> This is the project's *own* description of its level of
> completeness/reliability.  Warm fuzzy feelings it does not leave me
> with.
> 
> I'm prepared to believe that core git is reasonably well debugged by
> now, but I have little confidence in its ability to interact with
> cvs in either direction.  It doesn't look like upstream has put much
> work into getting the bugs out of that.  (There's no reason to think
> they would care much about it...)  If we make that transition I
> think it will have to be all-or-nothing.

+1 for all.  Right when we branch 8.5 would be great :)

> > Something you will definitively not like about Git is that we will
> > lose the $PostgreSQL$ expansion stuff -- and there's no equivalent
> > functionality AFAIK.
> 
> Well, that particular thing always struck me as something we did
> because we could, not because there was any important requirement
> for it.

What's it doing exactly?  Is there some way to get similar
functionality in git?

Cheers,
David.
-- 
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david(dot)fetter(at)gmail(dot)com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Responses

pgsql-www by date

Next:From: Alvaro HerreraDate: 2009-05-18 16:50:04
Subject: Re: Problem in GIT mirror (was Re: pgsql: Fix all theserver-side SIGQUIT handlers ...)
Previous:From: Alvaro HerreraDate: 2009-05-18 15:46:45
Subject: Re: Content on wiki page

pgsql-committers by date

Next:From: Alvaro HerreraDate: 2009-05-18 16:50:04
Subject: Re: Problem in GIT mirror (was Re: pgsql: Fix all theserver-side SIGQUIT handlers ...)
Previous:From: Andrew DunstanDate: 2009-05-18 16:22:21
Subject: Re: pgsql: Add some instructions on how to customize emacs for working on

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