From: "Marco Costalba" <mcostalba@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: That improved git-gui blame viewer..
Date: Wed, 13 Jun 2007 13:11:16 +0200 [thread overview]
Message-ID: <e5bfff550706130411g151b76e3sa2e351aff5dbb35b@mail.gmail.com> (raw)
In-Reply-To: <7v645thto7.fsf@assigned-by-dhcp.pobox.com>
On 6/12/07, Junio C Hamano <gitster@pobox.com> wrote:
>
> However, adding a new option to "git log" so that you can say
> 'git log --single-follow=$this_file_at_the_tip $branch' is a
> separate matter. I think it is a sensible thing to do. But
> even if we do that, I think --single-follow should limit itself
> to the rename following of "diff -M/-C" style. It is insane to
> include another path only because the result did copy&paste only
> a handful lines out of during its history.
>
Some weeks ago I've started to experiment with git-log as a
replacement for git-rev-list (as suggested by Linus in a thread).
I found some problems and so I stopped, but I think it's time to give
it another look.
Maybe this week-end I'll do some testing.
Marco
next prev parent reply other threads:[~2007-06-13 11:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 18:26 That improved git-gui blame viewer Linus Torvalds
2007-06-09 18:29 ` Junio C Hamano
2007-06-11 6:42 ` Shawn O. Pearce
2007-06-11 15:46 ` Linus Torvalds
2007-06-11 16:05 ` Junio C Hamano
2007-06-12 6:16 ` Marco Costalba
2007-06-12 6:52 ` Junio C Hamano
2007-06-12 11:27 ` Marco Costalba
2007-06-12 11:58 ` Marco Costalba
2007-06-12 13:53 ` Shawn O. Pearce
2007-06-12 19:14 ` Junio C Hamano
2007-06-13 11:11 ` Marco Costalba [this message]
2007-06-13 12:44 ` Marco Costalba
2007-06-13 12:45 ` Johannes Schindelin
2007-06-13 14:08 ` Marco Costalba
2007-06-13 14:58 ` Johannes Schindelin
2007-06-13 16:18 ` Marco Costalba
2007-06-13 16:40 ` Johannes Schindelin
2007-06-13 16:27 ` Josef Weidendorfer
2007-06-13 16:50 ` Johannes Schindelin
2007-06-13 16:54 ` Josef Weidendorfer
2007-06-13 17:05 ` Johannes Schindelin
2007-06-13 18:17 ` Josef Weidendorfer
2007-06-13 18:34 ` Johannes Schindelin
2007-06-13 17:17 ` Junio C Hamano
2007-06-14 5:17 ` Shawn O. Pearce
2007-06-13 23:20 ` Jakub Narebski
2007-06-14 6:24 ` Marco Costalba
2007-06-13 11:03 ` Marco Costalba
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=e5bfff550706130411g151b76e3sa2e351aff5dbb35b@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
--cc=torvalds@linux-foundation.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).