2013/5/7 Alaric Snell-Pym:
> Semi-relatedly, I have an ignore glob set that ignores "*~" backup files
> that Emacs makes, as many do. However, I often work in a pattern of
> creating a bunch of files with the same base name and different
> extensions - such as foo.c and foo.h - and then have to do "fossil add
> foo.c foo.h" as "fossil add foo.*" will pick up the .c~ and .h~ files as
> well as the .c and .h. Even if I put an explicit "--ignore" on the
> command line, which I am presuming is only applied when fossil recurs
> into a subdirectory and gets its own directory listings of files.
>
> So, should "fossil add" automatically strip (perhaps with a warning)
> files passed to its command line that match the ignore-glob, unless a
> "--force" is specified?
Please try:
<https://www.fossil-scm.org/index.html/info/24effbc370>
When trying to "fossil add" files that are expected to be ignored,
most logical would be to ask confirmation first. This immediately
makes the -f|--force flag a logical addition: in most other commands
this flag is used to disable configuration dialogs, so does it here.
I think you will like this..... I do!
Example (assuming *.o is in "clean-glob" pattern):
$ touch src/foo.c src/foo.o src/foo.h
$ fossil add src/foo.*
file "src/foo.o" should be ignored. Add it (a=all/y/N)? n
ADDED src/foo.c
ADDED src/foo.h
$ fossil add src/foo.* -f
ADDED src/foo.c
ADDED src/foo.h
ADDED src/foo.o
$
Feedback appreciated!
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
