Brian May <[EMAIL PROTECTED]> writes: >>>>>> "Derek" == Derek Scherger <[EMAIL PROTECTED]> writes: > > Derek> Does it make sense to anyone that 'mtn ls unknown' lists the entire > Derek> tree below an unknown directory? > > Seems to make sense IMHO. > > Derek> I'm sure there are possible down-sides to this change. For example > it > Derek> changes the semantics of things like 'mtn ls unknown | mtn xargs > add' > Derek> and 'mtn add --unknown'. However, add recently became non-recursive > Derek> and I wonder if this makes more sense with that change anyway. > > As long as there is still as recursive version, I am happy.
I think the default ought to be the recursive one (as it seems to be for other systems (those that I use, anyway)). However, I've no idea whether either option is better in any objective sense. > Also for ls known and ls unknown, I would really like it if pathnames > were relative to the current directory, not the base directory, ie: > > [EMAIL PROTECTED]:~/tree/config/include$ mtn ls known . > include > include/config.sh > include/filter Jonathan Shapiro argued against that, based on some experience with OpenCM. It annoys me, too, but I can see the arguments on both sides. It doesn't seem at all clear that what monotone does now is wrong. A possibly related change (to the "ls unknown" and "ls ignored" behaviours) would be to ignore entirely subdirectories with a _MTN directory. I guess that would be uncontroversial? [...] _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
