From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 36: providing both CVS and Subversion?
Date: Mon, 11 Apr 2005 21:42:52 +0100 [thread overview]
Message-ID: <20050411214252.3dca4edc@snowdrop> (raw)
In-Reply-To: <200504112223.32908.trapni@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2142 bytes --]
On Mon, 11 Apr 2005 22:23:29 +0200 Christian Parpart <trapni@gentoo.org>
wrote:
| On Monday 11 April 2005 8:26 am, Ciaran McCreesh wrote:
| > On Sun, 10 Apr 2005 23:57:12 +0200 Christian Parpart
| > <trapni@gentoo.org>
| > wrote:
| > | > SVN uses transactions and
| > | > changesets. These make a heck of a lot more sense if they're
| > | > done on a per project basis.
| > |
| > | reason?
| >
| > Because you can pull out a meaningful and relevant changeset without
| > having to arse around with path prefixes.
|
| Do you have to? If so, why?
Well, surprisingly enough, one of the main reasons we use these version
control things is so that we can see *what changed*. It's a hell of a
lot easier to do this when you can just say "show me everything that
changed in the foo project between three days ago and today" rather than
having to worry about adding in extra selections to pick a project path.
| > | > Unlike with CVS, this makes a big difference -- SVN
| > | > revision IDs are actually meaningful,
| > |
| > | SVN repository IDs represent the state of the whole repository at
| > | a given time, nothing more or less.
| >
| > Not repo IDs. Revision IDs.
|
| That's the one I meant. yeah.
And, said revision IDs are useful for keeping track of what's changed.
Or, at least, they are if you know that an update of 3 in the revision
number is equivalent to three changesets, which you don't if you use
multiple projects per repo.
| > | Hmm... besides, the ASF is just having a single repository for all
| > | their public projects (with about 1000+ contributors) w/o any
| > | problems.
| >
| > So we should make the same mistakes as them? Sure, a single repo
| > would be usable, but multiple repos would be a heck of a lot better.
|
| Seriousely, this is plain low FUD unless you can give me a decent
| argument on why the ASF made a mistake here.
One big repository is harder to work with. It's that simple.
--
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 --]
next prev parent reply other threads:[~2005-04-11 20:44 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
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 [this message]
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=20050411214252.3dca4edc@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