On Fri, Dec 07, 2007 at 02:05:15PM -0500, Thomas Harning wrote:
I concur. There is one case that this seems to dodge. What about the case
where you are in:
/test/test_2 where /test is not tracked...
This should probably show "./../" not just "./" , right?
It already says "../", which is correct:
$ git init
$ mkdir test && cd test
$ touch file
$ mkdir test2 && cd test2
$ git status
...
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# ../
There's no point in ever saying "./" _except_ in the case where the
output would be totally blank, since there is no way to tell that it is
an output line.
Personally, I don't like either the "../" or the "./", but I actually
think the relative paths are less readable than the full paths in
general.
-Peff