On Dec 16, 2007 1:17 PM, Brian W. Fitzpatrick <fitz@red-bean.com> wrote:
> See ### comment below:
>
> $ svn cl moo doggie1.txt
> Path 'doggie1.txt' is now a member of changelist 'moo'.
>
>
> $ svn st --changelist moo
>
> --- Changelist 'moo':
> doggie1.txt
>
>
> ### The next line says it's removing doggie1.txt, but it adds it right back!
> $ svn cl moo doggie1.txt
> svn: warning: Removing 'doggie1.txt' from changelist 'moo'.
> Path 'doggie1.txt' is now a member of changelist 'moo'.
Right, we added the 'warning' line because people were worried that
running 'svn cl NEWLIST path' could accidentally move a file from one
changelist to another, without the user realizing it. So we added the
warning to say "by the way, you realize this thing was already in a
changelist, right?"
What you're seeing here is the odd combination of the warning plus
moving the thing to the changelist it was already in. Should we
special case that edge-case to say "doggie1.txt is already a member of
changelist 'moo'" ? Is that the confusion?
>
>
> $ svn st --changelist moo
>
> --- Changelist 'moo':
> doggie1.txt
>
>
> $ svn cl --remove doggie1.txt
> Path 'doggie1.txt' is no longer a member of a changelist.
>
>
> $ svn st --changelist moo
> subversion/svn/status-cmd.c:230: (apr_err=200024)
> svn: Unknown changelist 'moo'
Sure, everything else is as expected. If you remove all paths from a
changelist, the changelist ceases to exist.
Also, as a side note: running 'svn status' with no arguments will
show *all* changelists that can be discovered, which is sort of the
equivalent of running 'p4 opened'. I imagine that's much more the
norm than invoking 'svn st --changelist moo'.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 16 22:36:23 2007