From: Linus Torvalds <torvalds@osdl.org>
To: David Ho <davidkwho@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-whatchanged does not show merge result?
Date: Fri, 14 Oct 2005 11:39:30 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0510141138030.23590@g5.osdl.org> (raw)
In-Reply-To: <4dd15d180510141031n531b9e0enc8e7d668b1e61b83@mail.gmail.com>
On Fri, 14 Oct 2005, David Ho wrote:
>
> I was a little worried when I did git-whatchanged on a file and there
> was a hole in the history where the merge is. This reassured me that
> all changes to the file is accessible (I'm sure they are all stored
> safely in the repo =).
Btw, "git-whatchanged" really _can_ hide real stuff, namely when nothing
changed.
A commit that has no changes at all (which is quite possible) will never
be shown by git-whatchanged.
So in many ways, "git log" is the way to see all commits.
"git-whatchanged" is really just a way to see the _changes_, and by
defauly it ignores merges just because the changes are "complicated".
Linus
next prev parent reply other threads:[~2005-10-14 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4dd15d180510140929x2c69f61ag19a1409cfd993e7b@mail.gmail.com>
2005-10-14 16:33 ` git-whatchanged does not show merge result? David Ho
2005-10-14 17:13 ` Linus Torvalds
2005-10-14 17:31 ` David Ho
2005-10-14 18:39 ` Linus Torvalds [this message]
2005-10-14 17:24 ` Junio C Hamano
2005-10-14 17:39 ` David Ho
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=Pine.LNX.4.64.0510141138030.23590@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=davidkwho@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).