Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Michał Górny <mgorny@g.o>
Subject: Re: Portage Git migration - clean cut or git-cvsserver
Date: Wed, 23 May 2012 22:37:55 +0200
On Wed, 23 May 2012 15:25:54 -0500
William Hubbs <williamh@g.o> wrote:

> On Thu, May 24, 2012 at 01:07:08AM +0530, Arun Raghavan wrote:
> > I, for one, think we should stay with CVS and leave all this git
> > Linusware to the new-fangled Fedora kids with their fancy init
> > systems and tight coupling. CVS was good enough for my grandfather,
> > and it's good enough for you.
> 
> I hope this is sarcasm or a joke?

Obviously. His grandfather used SCCS.

-- 
Best regards,
Michał Górny
Attachment:
signature.asc (PGP signature)
Replies:
Re: Portage Git migration - clean cut or git-cvsserver
-- William Hubbs
References:
Portage Git migration - clean cut or git-cvsserver
-- Michael Weber
Re: Portage Git migration - clean cut or git-cvsserver
-- Alexey Shvetsov
Re: Portage Git migration - clean cut or git-cvsserver
-- Robin H. Johnson
Re: Portage Git migration - clean cut or git-cvsserver
-- Alexey Shvetsov
Re: Portage Git migration - clean cut or git-cvsserver
-- Chí-Thanh Christopher Nguyễn
Re: Portage Git migration - clean cut or git-cvsserver
-- Arun Raghavan
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Portage Git migration - clean cut or git-cvsserver
Next by thread:
Re: Portage Git migration - clean cut or git-cvsserver
Previous by date:
Re: Portage Git migration - clean cut or git-cvsserver
Next by date:
Re: Portage Git migration - clean cut or git-cvsserver


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.