From: Domagoj Stolfa <domagoj.stolfa@gmail.com>
To: git@vger.kernel.org
Subject: Re: Possible git blame bug?
Date: Mon, 13 Mar 2017 21:46:14 +0100 [thread overview]
Message-ID: <20170313204614.GA66050@workstation> (raw)
In-Reply-To: <20170313204401.GB80633@workstation>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
Hello,
> > The question is whether this is a bug or not, as --since=<year> might not be a
> > valid filter.
>
> I do not think blame ever was designed to work with --since, so that
> is indeed the case.
>
> Making it work with --since=<date> might be a worthy addition.
> Patches welcome.
Thanks for the information. I wasn't aware that it wasn't designed with that in
mind, though it would indicate to me that --since seems to work with git-blame
according to [1], but expects a date, as I have usually been using it. It also
seems to produce correct results on FreeBSD 12.0-CURRENT with git 2.11.1, except
when given a filter such as --since=<year>, in which case perhaps nothing should
be displayed?
Could you please clarify which bits wouldn't work with --since in git-blame?
[1] https://www.git-scm.com/docs/git-blame
--
Best regards,
Domagoj Stolfa
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-03-13 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 20:11 Possible git blame bug? Domagoj Stolfa
2017-03-13 20:38 ` Junio C Hamano
[not found] ` <20170313204401.GB80633@workstation>
2017-03-13 20:46 ` Domagoj Stolfa [this message]
2017-03-13 21:29 ` Junio C Hamano
2017-03-13 21:44 ` Domagoj Stolfa
2017-03-13 22:19 ` Junio C Hamano
2017-03-13 22:46 ` Junio C Hamano
2017-03-13 23:08 ` Domagoj Stolfa
2017-03-13 23:15 ` Junio C Hamano
2017-03-13 23:19 ` Domagoj Stolfa
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=20170313204614.GA66050@workstation \
--to=domagoj.stolfa@gmail.com \
--cc=git@vger.kernel.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).