On Thu, Dec 23, 2010 at 3:44 PM, Richard Hipp <[email protected]> wrote:
> For a long time now, Fossil has accepted two possible names for the > check-out database: "_FOSSIL_" or ".fos". You can see this by doing: > i didn't know that, but the _FOSSIL_ file has never given me any problems, so i always ignore it (which is why i ended up hosing it today ;). > I'm wondering if I should make ".fos" the default instead of "_FOSSIL_". > Would xargs have picked up on the "dot-file" named ".fos" as it did with > _FOSSIL? Would the use of .fos instead of _FOSSIL_ have prevented this > problem? > The effect is the same: step...@ludo:~/cvs/fossil/whio$ touch .fos step...@ludo:~/cvs/fossil/whio$ find . -type f | grep fos ./.fos Changing that might help in cases where wildcards are used (e.g. if i had passed (-name '*.[ch]') to find), but if i had used a wildcard in the first place i wouldn't have hosed by _FOSSIL_. i didn't use a wildcard because i wanted to sed/perl my Makefiles and exported wiki pages at the same time. i.e. i got lazy and paid the price. Again, i don't consider this to be a fossil problem, but stupid user error. IMO there's no need to change it. It might break someone else's scripts (or documentation) which uses the current name, and wouldn't make any difference for the majority of us. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
