All of lore.kernel.org
 help / color / mirror / Atom feed
* history of a renamed file
@ 2008-04-23 13:02 Christoph Duelli
  2008-04-23 13:25 ` Jakub Narebski
  0 siblings, 1 reply; 4+ messages in thread
From: Christoph Duelli @ 2008-04-23 13:02 UTC (permalink / raw)
  To: git

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?

Thank you, best regards
Christoph

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: history of a renamed file
  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
  0 siblings, 2 replies; 4+ messages in thread
From: Jakub Narebski @ 2008-04-23 13:25 UTC (permalink / raw)
  To: Christoph Duelli; +Cc: git

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).

-- 
Jakub Narebski
Poland
ShadeHawk on #git

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: history of a renamed file
  2008-04-23 13:25 ` Jakub Narebski
@ 2008-04-23 13:45   ` Christoph Duelli
  2008-04-23 14:05   ` Teemu Likonen
  1 sibling, 0 replies; 4+ messages in thread
From: Christoph Duelli @ 2008-04-23 13:45 UTC (permalink / raw)
  To: Jakub Narebski; +Cc: git

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: history of a renamed file
  2008-04-23 13:25 ` Jakub Narebski
  2008-04-23 13:45   ` Christoph Duelli
@ 2008-04-23 14:05   ` Teemu Likonen
  1 sibling, 0 replies; 4+ messages in thread
From: Teemu Likonen @ 2008-04-23 14:05 UTC (permalink / raw)
  To: Jakub Narebski; +Cc: Christoph Duelli, git

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-04-23 14:06 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.