this behaviour seems buggy (or I miss some crucial point):
under certain circumstances `fossil extras' and `fossil changes' don't
report the file name of the affected files correctly. specifically from
within
a subdir, if the behaviour is triggered, fossil reports only the dirname,
i.e.
`..'
instead of the expected
`../abc' (where `abc' is the untracked file residing in the root dir of
the checkout).
copy+paste example reproducing the problem (it does for me ...):
8<----------------------------
mkdir tmp
cd tmp
touch abc def.txt
mkdir abcdir
fossil init db.fossil
fossil open db.fossil
fossil extras #`abc' correctly reported here...
cd abcdir
fossil extras #... but not here (`..' shown instead of `../abc')
8<----------------------------
it seemingly has to do with the fact that die affected file's name is
identical to a leading string of the subdir name (chosing different
name for the subdir restores sane behaviour)
observed with
This is fossil version 1.28 [af995cf7ea] 2014-02-28 08:08:11 UTC
under MacOS
can someone confirm this? bug or non-bug? any ideas?
j.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
