git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Miles Bader <miles@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: git-diff new files (without using index)
Date: Sun, 5 Aug 2007 00:08:41 -0400	[thread overview]
Message-ID: <20070805040841.GG9527@spearce.org> (raw)
In-Reply-To: <87r6miljfr.fsf@catnip.gol.com>

Miles Bader <miles@gnu.org> wrote:
> Thanks for the tip (I guess I can roll my own "git-diff-uncached"
> script)!

Indeed, Git is quite scriptable.  ;-)
 
> The above sort of quirkiness does seem kind of a wart though; in my
> (admittedly limited, using git) experience this sort of thing really
> reduces the utility of the index, and I often end up feeling like it's
> just getting in the way as a result.  Does adding something like a
> "git-diff -N" option seem a _bad_ idea?

I'm not interested in such an option.  Typically if I want a
diff on a new untracked file I actually want that file in my next
commit anyway.  So I'm usually staging it into the index along with
everything else that I have modified.  In which case this quirkiness
isn't really a quirk at all.  Its just not an issue to me.

If you want to try adding it, go right ahead.  The source for git
is stored in git and available from many places.  :-)

-- 
Shawn.

  reply	other threads:[~2007-08-05  4:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05  3:42 git-diff new files (without using index) Miles Bader
2007-08-05  3:52 ` Shawn O. Pearce
2007-08-05  4:00   ` Miles Bader
2007-08-05  4:08     ` Shawn O. Pearce [this message]
2007-08-05  4:20       ` Junio C Hamano
2007-08-05  4:37         ` Miles Bader

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=20070805040841.GG9527@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=miles@gnu.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).