git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustaf Hendeby" <hendeby@gmail.com>
To: git@vger.kernel.org
Subject: Difference in how "git status" and "git diff --name-only" lists filenames
Date: Sun, 2 Dec 2007 15:04:06 +0100	[thread overview]
Message-ID: <bf7b2dda0712020604x209d6665i9ab58b32834b2cee@mail.gmail.com> (raw)

A while ago 'git status' was patched to report relative pathnames.  (I
like that change it makes cut'n'paste easier.)  However, 'git diff
--name-only' and 'git diff --name-status' (other commands as well),
which gives in a sense similar output has not been changed the same
way.  Is this intentionally, or just because no one has stepped up and
provided a patch?  If the difference is to stay, maybe this should be
reflected in the help texts to avoid any confusion.

/Gustaf

             reply	other threads:[~2007-12-02 14:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-02 14:04 Gustaf Hendeby [this message]
2007-12-02 18:44 ` Difference in how "git status" and "git diff --name-only" lists filenames Junio C Hamano
2007-12-06 16:36   ` Gustaf Hendeby

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=bf7b2dda0712020604x209d6665i9ab58b32834b2cee@mail.gmail.com \
    --to=hendeby@gmail.com \
    --cc=git@vger.kernel.org \
    /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).