public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@wasabisystems.com>
To: Benjamin Kosnik <bkoz@redhat.com>
Cc: "Zack Weinberg" <zack@codesourcery.com>,
	jason-swarelist@molenda.com, per@bothner.com,
	overseers@sources.redhat.com
Subject: Re: switch to subversion?
Date: Fri, 19 Dec 2003 20:23:00 -0000	[thread overview]
Message-ID: <m3d6ak8slq.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20031219140858.7bdd8109.bkoz@redhat.com>

Benjamin Kosnik <bkoz@redhat.com> writes:

> >General agreement with this, also I don't think subversion scales to a
> >project the size of gcc (much less /cvs/src!) yet, and I am currently
> >thinking that monotone (http://www.venge.net/monotone/) will suit our
> >purposes better.  It isn't ready yet either, though.
> 
> I would love to see gcc start testing monotone. I concurr: it's looking
> very sharp. (It's also been tested with the gcc repository, which gives
> me hope.)

I would like to see a free version control system which implements
change-sets.  (My understanding is that Bitkeeper implements them.)

In my mind, a change-set is essentially a large patch file (it would
typically implement a particular feature).  Applying a change set
essentially means running patch.  A version control system which
supports change-sets makes it easy to create and to apply change-sets.
It should do version tracking of change-sets, so that a single working
tree can be the combination of several change-sets, and it should be
possible to update a working tree to a new copy of a particular
change-set.

The application of change-sets is trickier than a three-way merge,
because there is no known ancestor revision, so conflicts are hard to
handle.  But the concept is powerful.

I wouldn't be very enthusiastic about switching to a new version
control system if it didn't support change-sets.  While I'm ready to
believe that subversion and monotone are a better CVS, in my opinion
CVS itself still works well enough for what it does.


Ian

  reply	other threads:[~2003-12-19 20:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 19:38 Per Bothner
2003-12-19 19:42 ` Jason Molenda
2003-12-19 19:48   ` Zack Weinberg
2003-12-19 20:09     ` Benjamin Kosnik
2003-12-19 20:23       ` Ian Lance Taylor [this message]
2003-12-20  3:08         ` Jim Blandy
2003-12-20  3:51           ` Zack Weinberg
2003-12-31 17:02         ` Andrew Cagney
2003-12-19 20:50     ` Joseph S. Myers
2003-12-19 22:25       ` Zack Weinberg
2003-12-20  3:05     ` Jim Blandy
2003-12-20  3:50       ` Zack Weinberg
2003-12-20  3:03   ` Jim Blandy
2003-12-20  3:14   ` Jim Blandy

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=m3d6ak8slq.fsf@gossamer.airs.com \
    --to=ian@wasabisystems.com \
    --cc=bkoz@redhat.com \
    --cc=jason-swarelist@molenda.com \
    --cc=overseers@sources.redhat.com \
    --cc=per@bothner.com \
    --cc=zack@codesourcery.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).