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

Re: proposal: changelist feature

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-04-18 19:52:03 CEST

On 4/18/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> On 4/17/06, Ben Collins-Sussman <sussman@red-bean.com> wrote:
>
> > An initial super-simple implementation of such a feature could be
> > nothing more than attaching a changelist name as an 'entry-prop' in
> > .svn/entries, or something similar. Later on, if we wanted to get
> > fancy and try to make the svn client also be "super quick" and avoid
> > crawls, we *could* have the client track changelists in a central
> > registry, such as in ~/.subversion/. Of course, the tradeoff is that
> > it takes us one more step towards the idea of working copies being
> > non-divisible and non-portable. Not sure we want to open that
> > discussion. :-)
>
> A few more ideas that occurred to me...
>
> Can files be added to a changelist if they haven't been modified?

I'd say 'no', and I put that in my demo. It keeps life simpler.

> What happens when a file has been added to a changelist, then is
> reverted?

It loses the changelist tag.

> If a file is a member of a changelist and it's committed, is it
> removed from the changelist?
>

Yes. A very strange corner case, though, since presumably the whole
reason it was part of the changelist in the first place was so that it
could be committed as part of a larger change.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 18 19:55:51 2006

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.