From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-pickaxe: blame rewritten.
Date: Thu, 12 Oct 2006 08:58:54 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610120854440.3952@g5.osdl.org> (raw)
In-Reply-To: <7v7iz5rk4b.fsf@assigned-by-dhcp.cox.net>
On Thu, 12 Oct 2006, Junio C Hamano wrote:
> +
> +SYNOPSIS
> +--------
> +'git-pickaxe' [-c] [-l] [-t] [-f] [-n] [-p] [-L n,m] [-S <revs-file>] [--] <file> [<rev>]
Btw, could we please get rid of this horrible command line syntax.
Pretty much _every_ other git command takes the form
git cmd [<rev>] [--] <path>
but for some reason annotate and blame (and now pickaxe) do it the wrong
way around, and do
git cmd [--] <path> [<rev>]
which is just irritating to somebody who has grown very used to being able
to specify revisions first.
(I'd actually also like to have a range-modifier, so that I could do
git annotate --since=2.weeks.ago v2.6.18.. <path>
that didn't go back beyond a certain point, so the command line syntax
actually _does_ matter - even if we don't support that now, having the
regular command line syntax means that we -could- support it some day).
Linus
next prev parent reply other threads:[~2006-10-12 15:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 8:52 [PATCH] git-pickaxe: blame rewritten Junio C Hamano
2006-10-12 15:58 ` Linus Torvalds [this message]
2006-10-12 19:09 ` Junio C Hamano
2006-10-12 20:10 ` Luben Tuikov
2006-10-13 20:31 ` Junio C Hamano
2006-10-13 5:35 ` Junio C Hamano
2006-10-12 19:31 ` Luben Tuikov
2006-10-12 22:20 ` Junio C Hamano
2006-10-13 20:54 ` Luben Tuikov
2006-10-13 21:38 ` Junio C Hamano
2006-10-13 21:59 ` Luben Tuikov
2006-10-13 22:50 ` Junio C Hamano
2006-10-13 0:06 ` Junio C Hamano
2006-10-13 1:04 ` Luben Tuikov
2006-10-13 1:45 ` Junio C Hamano
2006-10-12 21:55 ` Jakub Narebski
2006-10-12 22:47 ` Petr Baudis
2006-10-12 23:35 ` 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.0610120854440.3952@g5.osdl.org \
--to=torvalds@osdl.org \
--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).