From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: file rename causes history to disappear
Date: Wed, 06 Sep 2006 20:52:51 +0200 [thread overview]
Message-ID: <edn5dd$c4s$2@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0609061131100.27779@g5.osdl.org
Linus Torvalds wrote:
>> git-rev-list could then output hash with current set of <filenames>, which
>> were given <filename> at the beginning, i.e.
>> <hash> -- <filename> [<filename>...]
>
> I would argue that "--follow" would be incompatible with having other
> <paths> listed. But maybe there is some sensible rule for what the
> combination means (show the listed paths _and_ the file we're following?)
> I dunno.
I'm not that sure. The output could be changed to, for example
<hash> SP <quoted-filename> [SP <quoted-filename> ...]
although I'm not sure if git can detect that two files were joined into one
(or, in reverse that one file was split into several; this doesn't matter
for following history of a file from top)
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".
As pathspecs doesn't change, there is no need to output them.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-06 18:55 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 [this message]
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='edn5dd$c4s$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).