From: Christoph Duelli <duelli@melosgmbh.de>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: history of a renamed file
Date: Wed, 23 Apr 2008 15:45:07 +0200 [thread overview]
Message-ID: <480F3D63.1040809@melosgmbh.de> (raw)
In-Reply-To: <m3y774putc.fsf@localhost.localdomain>
Jakub Narebski schrieb:
> Christoph Duelli <duelli@melosgmbh.de> writes:
>
>> Given a repo that contains a file x.c
>> that got renamed from
>> some/path/x.c
>> to
>> new/location/x.c
>>
>> 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?
>> When I say "gitk new/location/x.c" I get just the changes made
>> starting with the rename.
>> When I call "gitk" and look for the changeset, the rename is detected,
>> though. Therefore I hope that it is somehow possible to obtain the
>> complete file-specific history without truncation at renames.
>>
>> Any ideas?
>
> Try --follow option, see git-log(1), although I'm not sure if gitk
> supports it (it should).
Works, thank you!
--
Christoph Duelli
next prev parent reply other threads:[~2008-04-23 13:47 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 [this message]
2008-04-23 14:05 ` Teemu Likonen
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=480F3D63.1040809@melosgmbh.de \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.