git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: "Christian González" <christian.gonzalez@nerdocs.at>
To: Barret Rhoden <brho@google.com>, Thomas Gummerer <t.gummerer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: feature request: .blameignore
Date: Tue, 16 Apr 2019 18:33:45 +0200	[thread overview]
Message-ID: <48c54a71-ea00-82be-0844-9e1c76308e1e@nerdocs.at> (raw)
In-Reply-To: <7cb3e28d-2f4a-9fa8-d3c5-3b9184e53149@google.com>

[-- 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
> 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


[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 16605 bytes --]

      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]

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

  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 \
    --in-reply-to=48c54a71-ea00-82be-0844-9e1c76308e1e@nerdocs.at \
    --to=christian.gonzalez@nerdocs.at \
    --cc=brho@google.com \
    --cc=git@vger.kernel.org \
    --cc=t.gummerer@gmail.com \
    /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.
Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

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).