Hello,
> > Thanks for clearing this up. Is this documented somewhere, so that if it
> > happens
> > again I can point people to the docs that explain this behaviour?
>
> Is this from "git blame --help" sufficient?
>
> When you are not interested in changes older than version
> v2.6.18,
Domagoj Stolfa writes:
> Thanks for clearing this up. Is this documented somewhere, so that if it
> happens
> again I can point people to the docs that explain this behaviour?
Is this from "git blame --help" sufficient?
When you are not interested in changes
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 + 33) #ifndef _SYS_TIME_H_
> >
> > $ git blame
Junio C Hamano writes:
> Domagoj Stolfa writes:
>
>> 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
>>
Domagoj Stolfa writes:
> 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 + 33) #ifndef
Hello,
> >> The question is whether this is a bug or not, as --since= might not
> >> be a
> >> valid filter.
> >
> > I do not think blame ever was designed to work with --since, so that
> > is indeed the case.
>
> Actually, I do see that we had a cut-off based on rev->max_age since we
>
On Mon, Mar 13, 2017 at 1:38 PM, Junio C Hamano wrote:
> Domagoj Stolfa writes:
>
>> The question is whether this is a bug or not, as --since= might not be
>> a
>> valid filter.
>
> I do not think blame ever was designed to work with --since, so that
Hello,
> > The question is whether this is a bug or not, as --since= 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= might be a worthy addition.
> Patches welcome.
Thanks
Domagoj Stolfa writes:
> The question is whether this is a bug or not, as --since= 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= might be a worthy addition.
Hello,
yesterday I came across sort of a weird behaviour with git-blame. It would
appear when one queries the git blame on a specific file, such as:
$ git blame --since=
it will blame the entire file on some commit of that year, regardless of the
fact whether the commit has actually touched
10 matches
Mail list logo