From: Jakub Narebski <jnareb@gmail.com>
To: "Michał Łowicki" <mlowicki@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: GSoC - Better "git log --follow" support
Date: Sat, 19 Mar 2011 14:57:02 -0700 (PDT) [thread overview]
Message-ID: <m339mi6ago.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTi=n7e70UqYU+6wpG4cu95fsg39tVM6=7fpfdZFz@mail.gmail.com>
Michał Łowicki <mlowicki@gmail.com> writes:
> I'm looking at idea about better git log --follow support from
> https://git.wiki.kernel.org/index.php/SoC2011Ideas .There is something
> like this - "[.. ] it does not interact well with git's usual history
> simplification [...]". Can someone elaborate this? I've found History
> Simplification in git rev-list man but don't know yet about issues
> with --follow.
Well, '--follow' option to git-log is a bit of bolted-on hack.
It does work only for single file (it doesn't work e.g. for
directory), and it not always work correctly. For example
$ git log --follow gitweb/gitweb.perl
correctly follows gitweb history across gitweb.cgi => gitweb.perl
rename in 5d043a3 (gitweb: fill in gitweb configuration by Makefile,
2006-08-01), but it doesn't follow through subtree merging of gitweb
repository in 0a8f4f0 (Merge git://git.kernel.org/pub/scm/git/gitweb,
2006-06-10).
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-03-19 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 19:24 gsoc - Better git log --follow support Michał Łowicki
2011-03-19 21:57 ` Jakub Narebski [this message]
2011-03-21 12:24 ` Jeff King
2011-03-22 23:23 ` Michał Łowicki
2011-03-23 16:20 ` Jeff King
2011-03-23 16:58 ` Junio C Hamano
2011-03-23 17:06 ` Jeff King
2011-03-23 18:12 ` Junio C Hamano
2011-03-23 18:22 ` Jeff King
2011-04-13 21:04 ` Michał Łowicki
2011-04-15 4:06 ` Jonathan Nieder
2011-04-15 19:41 ` Michał Łowicki
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=m339mi6ago.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=mlowicki@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).