From: Bo Yang <struggleyb.nku@gmail.com>
To: Eli Barzilay <eli@barzilay.org>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
Eugene Sajine <euguess@gmail.com>,
Jacob Helwig <jacob.helwig@gmail.com>,
git@vger.kernel.org
Subject: Re: Re: git log -M -- filename is not working?
Date: Wed, 12 May 2010 22:49:03 +0800 [thread overview]
Message-ID: <AANLkTikhJO7MI9c5KezktpcMoQ86JPzAr4iT6_Yt2Ms3@mail.gmail.com> (raw)
In-Reply-To: <19434.48712.225245.305483@winooski.ccs.neu.edu>
Hi,
On Wed, May 12, 2010 at 10:42 PM, Eli Barzilay <eli@barzilay.org> wrote:
> (Looking at the description (in the SoC2010Ideas page) it wasn't clear
> to me whether this will be simple to use as log -- that is, just run
> some `git foo dir/{x,y,z}' or `git foo dir'.)
The idea here is that line level history will trace rename/copies of
multiple files and trace rename/copies of multiple files is obviously
a subset of tracing of it. So, what I mean is along implement such a
line level browser, I can do the --follow files case very well. :)
And as Jeff said in his mail, his implementation is necessary in speed
and please still use 'git log --follow -- pathspec' for whole file
history traversing.
Regards!
Bo
--
My blog: http://blog.morebits.org
prev parent reply other threads:[~2010-05-12 14:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 18:07 git log -M -- filename is not working? Eugene Sajine
2010-05-07 18:10 ` Jacob Helwig
2010-05-07 18:31 ` Eugene Sajine
2010-05-07 18:37 ` Eli Barzilay
2010-05-07 20:25 ` Matthieu Moy
2010-05-07 20:28 ` Jakub Narebski
2010-05-08 4:44 ` Jeff King
2010-05-08 5:12 ` Eli Barzilay
2010-05-08 5:30 ` Jeff King
2010-05-08 5:39 ` Junio C Hamano
2010-05-08 7:08 ` Eli Barzilay
2010-05-12 11:38 ` Jeff King
2010-05-12 12:01 ` Eli Barzilay
2010-05-12 12:49 ` Jeff King
2010-05-12 13:03 ` Jeff King
2010-05-12 14:35 ` Eli Barzilay
2010-05-12 16:07 ` Bo Yang
2010-05-12 16:45 ` Jeff King
2010-05-13 2:12 ` Bo Yang
2010-05-13 4:39 ` Eli Barzilay
2010-05-14 4:55 ` Jeff King
2010-05-14 5:05 ` Eli Barzilay
2010-05-12 13:06 ` Bo Yang
2010-05-12 13:09 ` Jeff King
2010-05-12 14:42 ` Eli Barzilay
2010-05-12 14:49 ` Bo Yang [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=AANLkTikhJO7MI9c5KezktpcMoQ86JPzAr4iT6_Yt2Ms3@mail.gmail.com \
--to=struggleyb.nku@gmail.com \
--cc=eli@barzilay.org \
--cc=euguess@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.helwig@gmail.com \
--cc=peff@peff.net \
/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).