On Wed, Apr 19, 2017 at 07:29:42AM +1000, [email protected] wrote:
> @Barry: True, but it's clumsy, since you have to specify every path, in
> full, in the global ignore-glob file. If you move a subproject to a
> different location in the directory tree, you have to remember to update
> the ignore-glob file.
>
That's true, but in some cases, the fossil ignore-glob is more useful.
Example:
*/obj/*
*.o
*.bak
Which will works for the whole repo.
I often do something like this to create or update my ignore-glob file:
fossil extra >> .fossil-settings/ignore-glob
vim .fossil-settings/ignore-glob
(cleanup the content added by "fossil extra" by replacing by the
most general glob pattern possible to get rid the extras and
keep some individual file from the list if needed, for the
exceptions)
But I agree that the per directory ignore file have it's advantage in
some situations.
>
> This is something I miss from Subversion (and Git, too, apparently) -
> the ability to set an ignore list for *just this directory*, and have
> that ignore list move around with the directory automatically.
>
>
Also true for the venerable CVS (.cvsignore files).
[snip]
--
Martin G.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users