John Griffin wrote:
> Okay,
>
> Let me ask two other questions then. Are Perforce style changelists on
> the subversion development path? I took a look at the Web site and did
> not see any mention of changelists. Are Perforce style changelists considered
> a best practice? If they are considered a "bad" way of doing things what is
> the best practice for simultaneously managing multiple sets of changes?
I don't think anyone is working on such a thing, and honestly I'm not
sure how it would be implemented.
In Perforce the info about the changelists are stored on the server, and
they're kept in sync as you 'p4 edit' the various things you're
changing. In Subversion the server doesn't track that kind of
information, so it would have to be maintained in the client.
The current working copy design doesn't lend itself to such things, so
it would have to be implemented at another level.
Implementing it in the standard client would probably not mesh well with
things like being able to move working copies or being able to take a
subset of a working copy and use it as a stand alone working copy, so
I'm skeptical of this ever happening as part of the standard command
line client.
There's no reason you can't do essentially the same thing yourself
though. Just keep a text file containing a list of each file that's
part of your changeset and use the 'svn commit --targets FILE'
functionality when you're committing the final change. If you want a
nicer front end to that functionality I imagine it could be pretty
easily scripted.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 16 15:45:20 2004