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

Re: Changelists: the next generation

From: Jack Repenning <jackrepenning_at_tigris.org>
Date: 2007-10-12 19:43:24 CEST

On Oct 12, 2007, at 10:19 AM, Mark Phippard wrote:

> On 10/12/07, Jack Repenning <jackrepenning@tigris.org> wrote:
>> svn changelist --work-on changelistname (or some such syntax):
>> meaning "any
>> modification I make from now on should automatically be added to
>> changelistname."
> This one I don't understand. When does SVN know you made a
> modification? Unless you just mean add/delete?

Hmm, good point. No, I don't just mean add/delete (nor even the
somewhat longer list of changes that SVN does know about immediately,
like say pset). I really do mean to include everything that will,
sooner or later, be committable, including file modifications.
Which, as you say, has some challenges for SVN.

Maybe it just means "changelistname becomes a temporary alias for --
no-changelist", and/or an implicit "svn changelist
currentactivechangelistname --no-changelist" whenever it gets switched.

The user work flow is something like:

  - set one task as "active"
  - work for a while
  - set a second task as "active"
  - work for a while
  - set a third task (or maybe back to the first) as "active"
  - work for a while
  - confirm which changes have been attributed to which tasks

We have this in the Eclipse world (as I know you're aware, Mark;-),
with the combination of Subclipse and Mylyn, but not everyone gets to
work in Eclipse, sad to say.

> I think this feature would be a little easier with a new WC design
> where it could be stored in a single place.

Wouldn't surprise me in the least.

Jack Repenning
Project Owner
"Subversion for the rest of OS X"
Received on Fri Oct 12 19:43:32 2007

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.