On 08/24/2011 04:36 PM, Daniel Shahaf wrote: > Neels J Hofmeyr wrote on Wed, Aug 24, 2011 at 22:04:11 +0200: >> On 08/24/2011 04:01 PM, Daniel Shahaf wrote: >>> Neels J Hofmeyr wrote on Wed, Aug 24, 2011 at 15:32:20 +0200: >>>> Changelists have been *designed* in the flipped-over wrong-way-round: they >>>> *include*, not exclude selected items. We'd have to implement this against >>>> its basic design. (Like using switch for externals, remember?) >>> >>> Changelists were designed to group files. What's fundamentally flawed in >>> >>> % svn cl foo A/mu ./iota >>> % svn commit --depth=empty A/mu ./iota --except-cl=foo >> >> Usually the code goes like "if there is a changelist, act on the node only >> when it is part of the changelist." ...well, it's just what I remember >> faintly, admittedly. Is that true? >> > > My recollection is that 'svn $subcommand foo --changelist bar' applies > to one of: > > - the subset of descendants of that are in changelist 'bar'; > - both to foo and to members of 'bar' > > where some subcommands behave differently than others.
There should be no difference in behavior between subcommands. The documented behavior of changelists is to operate as filters only. So, 'svn $subcommand foo --changelist bar' operates on the subset of would-be targets were --changelist not specified which are members of the specific changelist. This means, for example, that 'svn info --changelist foo' will show nothing because 'svn info' is depth-zero by default and directories can't be in changelists, rather than showing all children of $CWD which are in the 'foo' changelist. -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
