From: "Christian González" <firstname.lastname@example.org>
To: Barret Rhoden <email@example.com>, Thomas Gummerer <firstname.lastname@example.org>
Subject: Re: feature request: .blameignore
Date: Tue, 16 Apr 2019 18:33:45 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
> 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
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?
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 16605 bytes --]
prev parent reply other threads:[~2019-04-16 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 20:55 Christian González
2019-04-15 21:15 ` Thomas Gummerer
2019-04-15 21:56 ` Christian González
2019-04-16 14:52 ` Barret Rhoden
2019-04-16 16:33 ` Christian González [this message]
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:
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 \
* 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 inbox:
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).