From: Johannes Sixt <j.sixt@viscovery.net>
To: Petr Onderka <gsvick@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: gitk --follow doesn't show changes correctly
Date: Thu, 21 Jun 2012 15:09:17 +0200 [thread overview]
Message-ID: <4FE31CFD.1000208@viscovery.net> (raw)
In-Reply-To: <CAPyqok3Nh7jzwDS31xnFQm1h9=ttxmqoYt_tsLLUqpmi_4NWcQ@mail.gmail.com>
Am 6/21/2012 14:56, schrieb Petr Onderka:
> if I try to see the history of a file across copies by "gitk --follow file",
> it seems it shows the correct revisions (although disconnected),
> but for revisions that modify the file under some older name,
> the diff of those changes is not shown.
--follow is a bolted-on feature. Do not expect it to work according to
your expectations ;)
> For example, I have a file f1, modify it in revision A,
> then copy it to f2 and modify it in revision B,
> and finally modify f2 in revision C.
>
> If I execute "gitk --follow f2", I can see revisions A, B and C.
> But in revision B, the diff shown contains the whole of f2 (as a new file)
> and the diff for revision A is completely empty.
>
> What I'd like to see in revision B is the diff between f2 and f1 at that point
> and in revision A the diff for f1.
Turn off "Limit diffs to listed paths" in gitk's settings. Perhaps this
shows the changes (among the changes of all other files per commit, of
course).
-- Hannes
prev parent reply other threads:[~2012-06-21 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 12:56 gitk --follow doesn't show changes correctly Petr Onderka
2012-06-21 13:09 ` Johannes Sixt [this message]
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=4FE31CFD.1000208@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gsvick@gmail.com \
/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).