From: Christian González <christian.gonzalez@nerdocs.at>
Date: Tue, 16 Apr 2019 16:33:45 GMT
Subject: Re: feature request: .blameignore
Message-ID: <48c54a71-ea00-82be-0844-9e1c76308e1e@nerdocs.at>
In-Reply-To: <7cb3e28d-2f4a-9fa8-d3c5-3b9184e53149@google.com>


> I think there's a slight misunderstanding.  In the patchset that
> Michael and I are working on, the user specifies whole commits
> explicitly.  This is usually done with a file, but can also be done
> from the command line for "one-off" ignored commits.  That sounds like
> what you want.
>
> The heuristics come in when we try to pass blame for specific *lines*
> that an ignored commit touched.  We pass the blame to the parent
> commit, but we also want to match the lines to a specific line in the
> parent commit.  That way we can find the 'right' ancestor commmit. 
> We're not able to always identify the 'right' commit, hence the
> heuristics.
>
Oh - that's something different, yes - thank you for clarifying!
Misunderstanding on my side, yes. This is a really great feature! Is
there a vague time schedule for a release? Still this year?

Thanks!

Christian