Projects with *many* subrepos could serve of a feature like this to avoid "spilling" wrong code on wrong repos.
That has happened to me too; *our fault* for not entering into the subrepo. Either way, one is using "subrepos" pseudofeature and this mistake will be happen again and again and again. It is an important usability tip to me. I think your request considers both points 1) Emit a LOUD warning should be the default 2) add the file unless the user provides -f (or similar) Seems very simple to me to enhance "subrepos" feature. But addremove should be consistent too by implementing a --recursive (or similar) option to detect subrepos and applying the moves/removes on the corresponding subrepos. 2016-05-03 14:20 GMT-03:00 Matt Welland <mattrwell...@gmail.com>: > Given directory structure like this: > > fossildirparent > - fossilsubdir > > where fossilsubdir is fossil nested under fossildirparent > > If you cd to fossildirparent and do a fossil add of a file in fossilsubdir: > > cd fossildirparent > fossil add fossilsubdir/somefile.txt > > The file fossilsubdir/somefile.txt will be added to the fossildirparent repo > and not the fossilsubdir fossil. This might arguably be correct behavior but > 50% of the time it is actually not what the user wanted. > > My request is to one of the following: > > 1. Refuse to add the file unless the user provides -f (or similar force > switch) > 2. Emit a LOUD warning so that the user has a clue that what they did might > not be what they expected. > > Thanks. > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
