git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: file rename causes history to disappear
Date: Wed, 06 Sep 2006 16:54:44 -0700	[thread overview]
Message-ID: <7vpse85z5n.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0609061205100.27779@g5.osdl.org> (Linus Torvalds's message of "Wed, 6 Sep 2006 12:06:06 -0700 (PDT)")

Linus Torvalds <torvalds@osdl.org> writes:

> On Wed, 6 Sep 2006, Jakub Narebski wrote:
>> 
>> But --follow=<filename> with <pathspec> can be useful, e.g. when <pathspec> 
>> is a directory (or, perhaps in the future, glob), which would mean "follow
>> the contents indicated in starting hash by <filename>, and stop following
>> when it falls out outside given <pathspec>, in our case given directory".
>
> Yes, that would indeed make sense. The pathspec ends up being kept as a 
> "limiter", and basically tells you what the "context" for following is 
> allowed to be. 
>
> Color me convinced.

Likewise.

  reply	other threads:[~2006-09-06 23:54 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
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 [this message]
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=7vpse85z5n.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=torvalds@osdl.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).