From: Kevin Daudt <me@ikke.info>
To: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What does 'git blame --before <rev> -- <file>' supposed to mean?
Date: Thu, 24 Aug 2017 09:58:48 +0200 [thread overview]
Message-ID: <20170824075848.GG3839@alpha.vpn.ikke.info> (raw)
In-Reply-To: <1503254759.3881.9.camel@gmail.com>
On Mon, Aug 21, 2017 at 12:15:59AM +0530, Kaartic Sivaraam wrote:
> Hello all,
>
> I tried to do a 'git blame' on a file and wanted to see the blame
> before a particular revision of that file. I initially didn't know that
> you could achieve that with,
>
> $ git blame <rev> <file>
>
> I thought I need to pass the revision as a parameter so I tried (before
> looking into the documentation) the command found in the subject. It
> worked but to my surprise it had the same result as,
>
> $ git blame -- <file>
>
> I was confused and came to know from the documentation that blame
> doesn't have any '--before' option. That was even more surprising. Why
> does blame accept an option which it doesn't identify? Shouldn't it
> have warned that it doesn't accept the '--before' option? I guess it
> should not accept it because it confuses the user a lot as the could
> make it hard time for him to identify the issue.
>
> 'git blame' doesn't seem to be the only command that accepts options
> not specified in the documentation there's 'git show' for it's company,
>
> $ git show --grep 'regex'
>
> But the good thing with the above command is it behaves as expected. I
> suspect this should be documented, anyway.
>
> Thoughts ?
>
> --
> Kaartic
Git blame takes options that are fed to git rev-list, to limit the
commits being taken into account for blaming.
The man page shows "[--since=<date>]", which is one such option, but
before is valid as well.
git blame -h shows:
<rev-opts> are documented in git-rev-list(1)
and man git-blame shows under specifying ranges (emphasis mine):
When you are not interested in changes older than version v2.6.18,
or changes older than 3 weeks, *you can use revision range
specifiers similar to git rev-list*:
So these options are not documented under git blame, but git rev-list.
Perhaps the synopsis of man git-blame could be expanded so that that
it's clear it accepts rev-list options.
Kevin
next prev parent reply other threads:[~2017-08-24 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 18:45 What does 'git blame --before <rev> -- <file>' supposed to mean? Kaartic Sivaraam
2017-08-24 7:58 ` Kevin Daudt [this message]
2017-08-24 16: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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170824075848.GG3839@alpha.vpn.ikke.info \
--to=me@ikke.info \
--cc=git@vger.kernel.org \
--cc=kaarticsivaraam91196@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).