Re: A concern regarding the changelist feature

Yes the suggestion does smell a little like a weak implementation of
local branches...

That doesn't invalidate the argument that a changelist is a set of
changes that should go together and that moving a change intended for
one commit into another silently does sound like broken workflow - the
user should absolutely be warned as it's clearly going to be easy to
do accidentally if you have two large and complicated changelists in
play.

I'd consider throwing an error for a move to a new changelist and
providing a --force option to make it happen.

--
Talden
On 10/1/07, Tor Ringstad <torhr@pvv.org> wrote:
> [Michael Haggerty]
> > What would be really sweet would be a way to stash a selected
> > changelist away somewhere (e.g., as a patch) [...]
>
> Aren't these "advanced changelist" features just branches in disguise?
>
>
> - Tor -
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org