git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: file rename causes history to disappear
Date: Wed, 06 Sep 2006 19:11:48 +0200	[thread overview]
Message-ID: <edmvfv$lt7$2@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0609060858050.27779@g5.osdl.org

Linus Torvalds wrote:

> There's a huge difference between "pathname" and "inode". And git operates 
> on _pathnames_, not on inodes. So when you give a pathname specifier, 
> that's _exactly_ what it is. It's a pathname specifier, _not_ an "inode" 
> specifier.
> 
> And pathnames don't change. They're just names for paths to possibly 
> _find_ a file/inode. They can't be "renamed". The data that is found 
> behind a pathname may be moved to _another_ pathname (and we call that a 
> rename), but that doesn't change the original pathname in any way, shape, 
> or form.

So if/when git would have --follow option to git-log and git-diff-*, it
would be rather --follow=<filename>, rather than --follow -- <paths>?

git-rev-list could then output hash with current set of <filenames>, which
were given <filename> at the beginning, i.e.
  <hash> -- <filename> [<filename>...]
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  parent reply	other threads:[~2006-09-06 17:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06 14:52 file rename causes history to disappear Jeff Garzik
2006-09-06 15:05 ` Timo Hirvonen
2006-09-06 15:38 ` Linus Torvalds
2006-09-06 15:46   ` Jeff Garzik
2006-09-06 16:14     ` Linus Torvalds
2006-09-06 16:37       ` Linus Torvalds
2006-09-06 19:29         ` Junio C Hamano
2006-09-06 21:45           ` Randal L. Schwartz
2006-09-07  0:52             ` Junio C Hamano
2006-09-07 10:16           ` Alex Riesen
2006-09-06 17:11       ` Jakub Narebski [this message]
2006-09-06 18:34         ` Linus Torvalds
2006-09-06 18:52           ` Jakub Narebski
2006-09-06 19:06             ` Linus Torvalds
2006-09-06 23:54               ` Junio C Hamano
2006-09-06 19:25             ` Jakub Narebski

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='edmvfv$lt7$2@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /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).