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

Re: svn commit: r19645 - branches/changelist-feature/subversion/svn

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-05-16 17:54:33 CEST

On 5/16/06, Philip Martin <philip@codematters.co.uk> wrote:

> Related questions: do users expect to add files to a changeset before
> modifying them (much like the lock command) or is it something that
> gets done after the file has been modified?

Association with a changelist is a piece of temporary metadata which
is orthogonal to the file being modifed or not. You can (de)associate
a changelist at any time.

Note that this is a bit different than perforce, but I don't think
that's a bad thing. In perforce, a file is read-only until you 'p4
edit' it, which automatically causes the file to be associated with a
changelist. (If no changelist is specified by the user, then the file
becomes associated with a changelist named 'default'.)

> Should the command that
> adds files to a changeset skip unmodified files?

No. There's nothing wrong with attaching a changelist name to an
unmodified file.

> If it doesn't skip
> then what about if/when the command becomes recursive?

In the case of recursion, the only things that should be skipped, I
think, are unversioned items.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 16 17:55:07 2006

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