public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 36: providing both CVS and Subversion?
Date: Sun, 10 Apr 2005 19:34:27 +0100	[thread overview]
Message-ID: <20050410193427.43968e1d@snowdrop> (raw)
In-Reply-To: <200504102027.05326.trapni@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]

On Sun, 10 Apr 2005 20:27:03 +0200 Christian Parpart <trapni@gentoo.org>
wrote:
| Both have pros and cons. Well, the ASF has everyting converted into a
| single  repository and they seem to be just lucky with it. KDE is
| about to convert  everything into a single svn repos as well (for
| other reasons). For the Gentoo projects, it might make sense
| (administrative) to keep  everything into a single repository as well.
| However, providing each sub  project with its own repository will work
| around the single-point-of-failure  effect (in worst case) so it's
| likely to happen this way.

Nothing to do with single points of failure. SVN uses transactions and
changesets. These make a heck of a lot more sense if they're done on a
per project basis. Unlike with CVS, this makes a big difference -- SVN
revision IDs are actually meaningful, and you don't want to lock every
single Gentoo project whilst one person on a slow dialup connection does
a single transaction to a single project.

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-04-10 18:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10 16:39 [gentoo-dev] GLEP 36: providing both CVS and Subversion? Aaron Walker
2005-04-10 17:12 ` Ciaran McCreesh
2005-04-10 17:27   ` Patrick Lauer
2005-04-10 17:32     ` Ciaran McCreesh
2005-04-10 17:47       ` Christian Parpart
2005-04-10 17:44     ` Christian Parpart
2005-04-10 17:53       ` Ciaran McCreesh
2005-04-10 18:27         ` Christian Parpart
2005-04-10 18:34           ` Ciaran McCreesh [this message]
2005-04-10 21:57             ` Christian Parpart
2005-04-11  6:26               ` Ciaran McCreesh
2005-04-11 20:23                 ` Christian Parpart
2005-04-11 20:42                   ` Ciaran McCreesh
2005-04-11 21:32                     ` Christian Parpart
2005-04-12 18:50                     ` Paul de Vrieze
2005-04-12 18:57                       ` Ciaran McCreesh
2005-04-13  1:33                         ` Christian Parpart
2005-04-13  6:26                           ` Ciaran McCreesh
2005-04-13 13:03                             ` Aaron Walker
2005-04-13 14:46                               ` Christian Parpart
2005-04-10 18:14 ` Lance Albertson
2005-04-10 18:23   ` Ciaran McCreesh
2005-04-10 21:30   ` Daniel Drake
2005-04-10 21:35     ` Greg KH
2005-04-10 21:44       ` Christian Parpart
2005-04-10 22:08         ` Daniel Drake
2005-04-10 21:48       ` Patrick Lauer
2005-04-10 22:00         ` Lance Albertson
2005-04-10 22:20       ` Donnie Berkholz
2005-04-12 23:22     ` Nicholas Jones
2005-04-12 18:31 ` Paul de Vrieze

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050410193427.43968e1d@snowdrop \
    --to=ciaranm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox