<html>
<body>
Thanks Dustin<br><br>
Thanks for comments.<br><br>
I recall from some distant days getting a bit tangled in the unix
wildcard thing. I assumed if would work because an example add
command in <br>
David Roundy's Darcs 1.0.0 doc says <br><br>
% darcs add *.c Makefile.am configure.ac<br><br>
And I take you point about a partially controlled directory. I have
literally 1000's of small gifs in this site. And I archive them with
arj32 chapter archives which is a sort of poor cousin revision
control.Darcs would be much better for the text stuff, as it also only
really makes little sense to save incremental changes for htm/js/css
files. I realize I can do what I want by adding some extensions to the
boring file. I think I can also edit manually the first pending file
before doing "darcs record"<br><br>
Cheers<br>
Rob<br><br>
<br>
<blockquote type=cite class=cite cite><x-tab> </x-tab>My
guess is that this is due to the difference between wildcard handling
between UNIX and Windows. In UNIX, applications do not handle
wildcards. i.e. ``darcs add -r *.htm'' would not make sense to me
(a UNIX user) unless you had a bunch of directories named
something.htm<br><br>
<x-tab> </x-tab>I
personally think it's a little silly to put the burden of wildcard
expansion on the application, but I guess it's not quite as easy to
``find . -name \*.htm | xargs darcs add'' in Windows.<br><br>
<x-tab> </x-tab>One thing
you might consider, though, is that it's probably not that good of an
idea to have a directory that's only partially revision
controlled.</blockquote></body>
</html>