[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] restrictions rewrite
From: |
Richard Levitte - VMS Whacker |
Subject: |
Re: [Monotone-devel] restrictions rewrite |
Date: |
Sat, 25 Feb 2006 05:11:15 +0100 (CET) |
In message <address@hidden> on Thu, 23 Feb 2006 21:44:35 -0700, Derek Scherger
<address@hidden> said:
derek> There is also another branch off of this called
derek> net.venge.monotone.restrictions.wildcard-paths where I've
derek> replaced the --depth argument with optional recursive
derek> directories using a dir/... syntax suggested by njs on the
derek> wiki.
I fail to see how the dir/... syntax can replace --depth. How do you
express something like 'monotone log dir --depth=3' using the
recursive directory syntax? I personally have no problem with having
--depth removed, but I think you need to think about the consequences
of removing it.
Also, the ... thing, is it only meant to be at the end of a path
specification, or is it intended to be mixed in, like dir/.../foo.c,
or dir1/.../dir2/dir3.../dir4/foo.c, to take a more complicated
possibility?
derek> Without the trailing "/..." a directory could match only
derek> itsself (--depth=0) or possibly itsself and all of its
derek> immediate children non-recursively (--depth=1). Both of these
derek> seem like useful cases particularly in the "required parent"
derek> directory cases so some feedback on this would be great.
The more I think about it, the harder it is to decide. Maybe this
indicates that --depth shouldn't be removed after all?
Cheers,
Richard
-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.
--
Richard Levitte address@hidden
http://richard.levitte.org/
"When I became a man I put away childish things, including
the fear of childishness and the desire to be very grown up."
-- C.S. Lewis