From: Linus Torvalds <torvalds@osdl.org>
To: Fredrik Kuivinen <freku045@student.liu.se>
Cc: git@vger.kernel.org, junkio@cox.net
Subject: Re: [PATCH] git-blame: Kill warning "print_map defined but not used"
Date: Sun, 5 Mar 2006 10:58:19 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0603051054330.13139@g5.osdl.org> (raw)
In-Reply-To: <20060305111650.GC23448@c165.ib.student.liu.se>
Fredrik,
Three comments on "git-blame":
- you should use "-u -U 0" instead of "-u0" to avoid warnings from some
versions of GNU diff
- Please default to HEAD so that you don't need to say it.
- What I'd actually want to see is blame for a certain group of lines.
Ie, I'd like to see
git-blame --line=50-56 filename
which only shows those 7 lines. That would be wonderful for a visual
interface where you could mark off a few lines and say "follow these
backwards" kind of thing, and should make it more efficient than trying
to resolve the _whole_ file.
Hmm?
Linus
next prev parent reply other threads:[~2006-03-05 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 11:16 [PATCH] git-blame: Kill warning "print_map defined but not used" Fredrik Kuivinen
2006-03-05 18:58 ` Linus Torvalds [this message]
2006-03-05 22:45 ` Junio C Hamano
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=Pine.LNX.4.64.0603051054330.13139@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=freku045@student.liu.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).