From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: file rename causes history to disappear
Date: Wed, 06 Sep 2006 21:25:47 +0200 [thread overview]
Message-ID: <edn996$rfb$1@sea.gmane.org> (raw)
In-Reply-To: edn5dd$c4s$2@sea.gmane.org
Jakub Narebski wrote:
> 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'm not that sure. The output could be changed to, for example
> <hash> SP <quoted-filename> [SP <quoted-filename> ...]
The "<hash> -- <filename> [<filename>...]" was to allow the followed
<filename> to be pathspec for other command, for example
git-diff-tree --stdin
(if git-diff-tree accepts pathspec limiting on stdin, and not only
revisions, or pairs of revisions; according to 1.4.2 documentation
--stdin is for reading either one <commit> or a pair of <tree-ish>
separated with a single space from its input -- no pathspecs).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2006-09-06 19:59 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
2006-09-06 19:25 ` Jakub Narebski [this message]
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='edn996$rfb$1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.