git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: git@vger.kernel.org
Subject: Re: git-diff new files (without using index)
Date: Sun, 05 Aug 2007 13:00:24 +0900	[thread overview]
Message-ID: <87r6miljfr.fsf@catnip.gol.com> (raw)
In-Reply-To: <20070805035245.GE9527@spearce.org> (Shawn O. Pearce's message of "Sat\, 4 Aug 2007 23\:52\:45 -0400")

"Shawn O. Pearce" <spearce@spearce.org> writes:
>> If I add things to the index, I can use "git-diff --cached" to do it;
>> however I'd actually like to be able to do this _without_ updating the
>> index
>
> Use a temporary index:
...
> Another option is to just add everything, then reset the index:
...
> Granted if you had other files staged they just became unstaged
> and will need to be restaged...  the temporary index trick above
> avoids that.

Thanks for the tip (I guess I can roll my own "git-diff-uncached"
script)!

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?

Thanks,

-Miles

-- 
"Suppose He doesn't give a shit?  Suppose there is a God but He
just doesn't give a shit?"  [George Carlin]

  reply	other threads:[~2007-08-05  4:00 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 [this message]
2007-08-05  4:08     ` Shawn O. Pearce
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=87r6miljfr.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --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).