xplanation, it seems to make perfect sense. Thanks
again for the detailed explanation of the behaviour!
--
Best regards,
Domagoj Stolfa
signature.asc
Description: PGP signature
Hello,
> > For example, saying:
> >
> > $ git blame time.h --since=2017
> > ^e19f2a27ed8 (Domagoj Stolfa 2017-03-12 20:43:01 +0100 33) #ifndef
> > _SYS_TIME_H_
> >
> > $ git blame time.h --since=2016
> > ^21613a57af9 (bz 2016-03-13 21:26:18 +00
different. The problem with it is that
it mentions commits that haven't even touched the file though. Output with
commit hashes that have touched that file would be sensible, albeit wrong in the
sense that the user did not want to see that behaviour.
For example, saying:
$ git blame time.h --si
lts on FreeBSD 12.0-CURRENT with git 2.11.1, except
when given a filter such as --since=, 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 Sto
to:
$ git blame tcp_output.c --since=2017
^e19f2a27ed8 (Domagoj Stolfa 2017-03-12 20:43:01 +0100 29) *
@(#)tcp_output.c8.4 (Berkeley) 5/24/95
$ git blame tcp_output.c --since=2016
^e4bdb83e76c (jceel2016-03-13 19:50:17 + 29) *
@(#)tcp_output.c8.4 (Berkeley) 5/24/95
5 matches
Mail list logo