[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: changelists?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2001-07-11 19:40:08 CEST

Steinar Bang <sb@metis.no> writes:

> Just out of curiosity: are the "change-lists" mentioned in
> <http://subversion.tigris.org/servlets/ReadMsg?msgId=22670&listName=dev>
> the same thing as the "perforce" concept "changelists"?
> <http://www.perforce.com/perforce/doc.011/manuals/p4guide/07_changelists.html#1040380>

Philosophically, they are the same thing: they're both talking about a
set of changes made to files and tree-structure.

But Subversion isn't a changeset-engine like Bitkeeper or other SCM
tools. Subversion doesn't allow you to manipulate or store changesets
as first-class objects. Instead, modeling off of CVS, it "discovers"
the changelist by crawling your working copy at commit-time. The
changelist is then sent over the network and applied to the head tree
in the repository. (The repository is an array of trees; each tree
represents a single commit, and thus each changelist can be deduced by
comparing successive trees.)

That email you cite is over a year old. I'd suggest reading the
design document, or looking at more recent mails. :-)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:33 2006

This is an archived mail posted to the Subversion Dev mailing list.