From: Jakub Narebski <jnareb@gmail.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
"Lin, Ming M" <ming.m.lin@intel.com>,
Alex Riesen <raa.lkml@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git history and file moves
Date: Fri, 24 Oct 2008 15:13:02 -0700 (PDT) [thread overview]
Message-ID: <m3vdvhhc5s.fsf@localhost.localdomain> (raw)
In-Reply-To: <4911F71203A09E4D9981D27F9D8308580AA7FFFB@orsmsx503.amr.corp.intel.com>
"Moore, Robert" <robert.moore@intel.com> writes:
>
> Thanks,
> Bob
>
> >-----Original Message-----
>Michael J Gruber wrote:
>>Alex Riesen venit, vidit, dixit 10/22/08 13:19:
>>> 2008/10/22 Lin Ming <ming.m.lin@intel.com>:
>>>> I'm looking for a way to move files to a new directory and have the
>>>> full history follow the file automatically. Is this possible?
>>>>
>>>> I know about --follow, but I want the history to just follow the file
>>>> transparently. ...
>>>
>>> Of all Git tools, what does not do this "transparently" or "automatically"?
[...]
>>>> Also, we have a git web interface and we want the full
>>>> history for the moved files to be available.
>>>
>>> It is available. Whether it is shown is another question. git-web can
>>> be improved (or just configured?)
>>
>> By default, gitweb uses "-M" for diff. You can specify all options (-C,
>> -CC, -B) using "@diff_opts" in the config file for gitweb.cgi - if that
>> is what you are using. Is it?
>>
>> Anyways, using default configs for git log and gitweb.cgi both of them
>> show the full history (renames, history before and after) for me here,
>> using current git (1.6.0.3.514.g2f91b). What is your setup?
>
> Here's what we have:
>
> /var/www/cgi-bin/gitweb.acpica/gitweb.conf
>
> Containts this : GITWEB_CSS = "/icons/gitweb.css";
This fragment has nothing to do with rename (file movement) detection.
>
> What should we add to automatically get all file history?
While the 'commitdiff' view would, in default gitweb configuration,
contain information about file renames, currently 'history' view does
not support '--follow' option to git-log. It wouldn't be too hard to
add it, but it just wasn't done (well, add to this the fact that
--follow works only for simple cases).
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2008-10-24 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 2:02 git history and file moves Lin Ming
2008-10-22 11:19 ` Alex Riesen
2008-10-22 12:38 ` Michael J Gruber
2008-10-24 21:30 ` Moore, Robert
2008-10-24 21:43 ` Alex Riesen
2008-10-24 22:01 ` Moore, Robert
2008-10-24 22:13 ` Jakub Narebski [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=m3vdvhhc5s.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=raa.lkml@gmail.com \
--cc=robert.moore@intel.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.