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

Re: Adding changeset-like functionality to subversion

From: Noel Yap <yap_noel_at_yahoo.com>
Date: 2002-10-08 21:54:39 CEST

--- Brad Appleton <brad@bradapp.net> wrote:
The following is meant to confirm my understanding of
subversion as well as possibly helping the original
poster.

> My understanding of "changeset" functionality is
> that the "unit"
> of change that is "committed" to the repository is
> not at the
> individual file-level, but is instead at the
> logical-level and
> would include all the edits to all the files that I
> modified
> for a single coherent and consistent purpose (such
> as a 'fix'
> or 'enhancement' or some other 'change task').
>
> So maybe when I did a "commit", there would be a way
> to identify
> the change-set: either I specify the name (or cset
> identifier)
> and svn would imply that it means all the files that
> I've
> checked-out in my current workspace, or else I
> specify the
> cset-name and the set of modified files, and only
> those files
> are committed to the codebase.
>
> Either way, the resulting cset-name can then be used
> as a tag of
> sorts to refer to the set of files and their
> changes/revisions
> hat were committed. And some would also say that
> they must be
> "committed" as an atomic transaction.

From my scant understanding of subversion (and please
correct me if I'm wrong), subversion will version the
entire tree with each commit, so, assuming the set of
files within a commit operation comprises the change
set, the change set will be whatever is different
between one version of the tree and the next.

> I think the issue of 'order-dependency' is more of a
> function
> of whether or not I chose to do my work on a new
> branch (and
> hence check it out onto a new branch) or on an
> existing branch.

Task branches would modify the components of a change
set from "what's part of one commit" to "what's part
of all the commits to the branch".

Again, from what little I understand of subversion,
when that branch gets merged into main development,
the entire tree will be versioned (on the main branch)
and so, the change set will still be the difference
between one version of the tree and the next.

Can someone verify or discount my statements, please?

Thanks,
Noel

__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 8 21:55:15 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.