From: Jeff King <peff@peff.net>
To: Thomas Harning <harningt@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] quote_path: convert empty path to "./"
Date: Fri, 7 Dec 2007 15:49:37 -0500 [thread overview]
Message-ID: <20071207204937.GA20111@coredump.intra.peff.net> (raw)
In-Reply-To: <4759996B.2000300@gmail.com>
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
next prev parent reply other threads:[~2007-12-07 20:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 16:57 [PATCH] quote_path: convert empty path to "./" Jeff King
2007-12-07 18:54 ` Johannes Schindelin
2007-12-07 19:05 ` Thomas Harning
2007-12-07 20:49 ` Jeff King [this message]
2007-12-07 21:26 ` [PATCH] add status.relativePaths config variable Jeff King
2007-12-08 7:34 ` Junio C Hamano
2007-12-08 7:47 ` Junio C Hamano
2007-12-08 8:02 ` Jeff King
2007-12-08 8:05 ` Junio C Hamano
2007-12-08 8:45 ` Jeff King
2007-12-08 7:55 ` Jeff King
2007-12-08 8:14 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071207204937.GA20111@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=harningt@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).