Git development
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>
Subject: Re: git-log --full-history renamed-file
Date: Sat, 10 Mar 2007 06:14:02 +0000	[thread overview]
Message-ID: <200703100614.04526.andyparkins@gmail.com> (raw)
In-Reply-To: <est24q$p4n$1@sea.gmane.org>

On Saturday 2007, March 10, Jakub Narebski wrote:

> By the way, while it is fairly easy to follow one file, it is hard
> to follow directory or glob... and there is a trouble that one file
> might come from two files (as concatenation for example; but I don't
> think git can detect it with default values of rename detection
> heuristics).

That's not rename detection then though.

I know git is clever and has potential to be able to do rename detection 
even when it was rename-and-modify.  For me though, I always like to 
make the job of the VCS easier by doing the rename in a separate commit 
from the modify.

I'd really like it if git would deal with the easy, 100% rename case, 
even if it didn't deal with the 
rename-two-files-to-be-one-file-and-modify-the-result case. 



Andy
-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com

  parent reply	other threads:[~2007-03-10  6:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09 21:30 git-log --full-history renamed-file Jim Meyering
2007-03-09 22:20 ` Linus Torvalds
2007-03-10  0:55   ` Junio C Hamano
2007-03-10  1:40     ` Jakub Narebski
2007-03-10  2:14       ` Junio C Hamano
2007-03-10  2:14       ` Linus Torvalds
2007-03-10  6:14       ` Andy Parkins [this message]
2007-03-10  1:59   ` Junio C Hamano

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=200703100614.04526.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --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