All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Frederich <eric.frederich@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Get a git diff without taking index into account
Date: Wed, 18 Feb 2015 08:33:52 -0800	[thread overview]
Message-ID: <xmqqfva341sf.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAAoZyYPVopmP_bv7EZS912R4bxpzNm49_q0XXZXqa52dTDDM2Q@mail.gmail.com> (Eric Frederich's message of "Wed, 18 Feb 2015 10:42:20 -0500")

Eric Frederich <eric.frederich@gmail.com> writes:

> This is from "git help diff".  It seems to imply that I should be able to do it.
> It mentions nothing of the index.

Most of the documentation on early subcommands (and "git diff"
certainly is one of the early subcommands) were written back when
everybody knew that Git almost always talks about _tracked_ files
that are known to the index, and the only time it even cares about
untracked ones that are not in the index was when it tries to help
users by reminding what the user may have forgot to "git add".

Documentation pages do not bother repeating "this only looks at
tracked paths" for this reason; Git is about tracked files by
default.

Perhaps you can suggest how to improve the description of commands
without being too repetitive?

Thanks.

  reply	other threads:[~2015-02-18 16:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 14:57 Get a git diff without taking index into account Eric Frederich
2015-02-18 15:06 ` Eric Frederich
2015-02-18 15:37   ` Junio C Hamano
2015-02-18 15:42     ` Eric Frederich
2015-02-18 16:33       ` Junio C Hamano [this message]
2015-02-18 18:27         ` Eric Frederich
2015-02-18 18:32           ` Jeff King
2015-02-18 19:36             ` Eric Frederich
2015-02-18 21:38             ` Eric Frederich
2015-02-18 22:16               ` Junio C Hamano
2015-02-18 22:30               ` Jeff King

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=xmqqfva341sf.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=eric.frederich@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.