From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Separating "add path to index" from "update content in index"
Date: Fri, 22 Dec 2006 09:24:36 +0100 [thread overview]
Message-ID: <emg4j2$f8v$1@sea.gmane.org> (raw)
In-Reply-To: 7vfyb87bxg.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> And it is not just limited to adding the contents of a path that
> happened to be told git for the first time. Adding the contents
> of a path that was known to git also happens only when it is in
> a presentable good state. So running "git diff" and not seeing
> what I added before is a GOOD THING.
If I remember correctly the idea behind "intent to add" was to show
only that file was added (e.g. the "new file" line from extended diff
header) in "git diff" when file was added and not modified
(and no changes to "git diff HEAD").
Although I'm not sure if this wouldn't screw some use cases which
include something like "git diff > some-temporary-file"...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-22 8:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 20:33 GIT - error: no such remote ref refs/heads/TestBranch Sean Kelley
2006-12-19 22:06 ` Junio C Hamano
2006-12-20 22:31 ` Carl Worth
2006-12-20 22:36 ` Junio C Hamano
2006-12-20 22:57 ` Carl Worth
2006-12-20 23:36 ` Junio C Hamano
2006-12-21 6:55 ` Carl Worth
2006-12-21 10:49 ` Peter Baumann
2006-12-22 0:52 ` Junio C Hamano
2006-12-22 2:32 ` Separating "add path to index" from "update content in index" Carl Worth
2006-12-22 3:06 ` Sean
2006-12-22 5:06 ` Nicolas Pitre
2006-12-22 21:57 ` Carl Worth
2006-12-23 5:27 ` Nicolas Pitre
2006-12-24 21:38 ` Daniel Barkalow
2006-12-22 5:10 ` Junio C Hamano
2006-12-22 5:21 ` Shawn Pearce
2006-12-22 8:24 ` Jakub Narebski [this message]
2006-12-22 16:18 ` Carl Worth
2006-12-22 17:28 ` Nicolas Pitre
2006-12-22 16:55 ` Carl Worth
2006-12-23 2:56 ` Daniel Barkalow
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='emg4j2$f8v$1@sea.gmane.org' \
--to=jnareb@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).