From: Teemu Likonen <tlikonen@iki.fi>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Christoph Duelli <duelli@melosgmbh.de>, git@vger.kernel.org
Subject: Re: history of a renamed file
Date: Wed, 23 Apr 2008 17:05:26 +0300 [thread overview]
Message-ID: <20080423140526.GC3291@mithlond.arda.local> (raw)
In-Reply-To: <m3y774putc.fsf@localhost.localdomain>
Jakub Narebski wrote (2008-04-23 06:25 -0700):
> Christoph Duelli <duelli@melosgmbh.de> writes:
>
> > Is it possible (ideally with gitk) to view the complete history of
> > what is now new/location/x.c *including* the history of changes that
> > occurred when it stil was some/path/x.c?
> Try --follow option, see git-log(1), although I'm not sure if gitk
> supports it (it should).
gitk certainly accepts '--follow' but the option does not work as
expected. For example try
gitk --follow -- utf8.c
in the Git repository and get surprised. :-)
I noticed the problem two weeks ago and Adam Simpkins elaborated it
a bit. See http://thread.gmane.org/gmane.comp.version-control.git/79008
prev parent reply other threads:[~2008-04-23 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 13:02 history of a renamed file Christoph Duelli
2008-04-23 13:25 ` Jakub Narebski
2008-04-23 13:45 ` Christoph Duelli
2008-04-23 14:05 ` Teemu Likonen [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=20080423140526.GC3291@mithlond.arda.local \
--to=tlikonen@iki.fi \
--cc=duelli@melosgmbh.de \
--cc=git@vger.kernel.org \
--cc=jnareb@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