From: Barret Rhoden <brho@google.com>
To: git@vger.kernel.org
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"David Kastrup" <dak@gnu.org>, "Jeff King" <peff@peff.net>,
"Jeff Smith" <whydoubt@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Junio C Hamano" <gitster@pobox.com>,
"René Scharfe" <l.s.r@web.de>,
"Stefan Beller" <stefanbeller@gmail.com>,
"Michael Platings" <michael@platin.gs>
Subject: [PATCH v5 0/6] blame: add the ability to ignore commits
Date: Wed, 3 Apr 2019 12:02:01 -0400 [thread overview]
Message-ID: <20190403160207.149174-1-brho@google.com> (raw)
This patch set adds the ability to ignore a set of commits and their
changes when blaming. This can be used to ignore a commit deemed 'not
interesting,' such as reformatting.
The last patch in the series is an RFC, and the others could be merged
without it. That last patch changes the heuristic by which ignored
lines are attributed to specific lines in the parent commit. This
increases the likelihood of blaming the 'right' commit, where 'right' is
subjective.
The last patch needs a little work still - there's a TODO section in
its commit message. It includes some of Michael's code, so if we are
going to keep it, I'd like to sort out authorship correctly.
v4 -> v5
v4: https://public-inbox.org/git/20190226170648.211847-1-brho@google.com/
- Changed the handling of blame_entries from ignored commits so that you
can use any algorithm you want to map lines from the diff chunk to
different parts of the parent commit.
- fill_origin_blob() optionally can track the offsets of the start of
every line, similar to what we do in the scoreboard for the final
file. This can be used by the matching algorithm. It has no effect
if you are not ignoring commits.
- RFC of a fuzzy/fingerprinting heuristic, based on Michael Platings RFC
at https://public-inbox.org/git/20190324235020.49706-2-michael@platin.gs/
- Made the tests that detect unblamable entries more resilient to
different heuristics.
- Fixed a few bugs:
- tests were not grepping the line number from --line-porcelain
correctly.
- In the old version, when I passed the "upper" part of the
blame entry to the target and marked unblamable, the suspect
was incorrectly marked as the parent. The s_lno was also in
the parent's address space.
v3 -> v4
v3: https://public-inbox.org/git/20190212222722.240676-1-brho@google.com/
- Cleaned up the tests, especially removing usage of sed -i.
- Squashed the 'tests' commit into the other blame commits. Let me know
if you'd like further squashing.
v2 -> v3
v2: https://public-inbox.org/git/20190117202919.157326-1-brho@google.com/
- SHA-1 -> "object name", and fixed other comments
- Changed error string for oidset_parse_file()
- Adjusted existing fsck tests to handle those string changes
- Return hash of all zeros for lines we know we cannot identify
- Allow repeated options for blame.ignoreRevsFile and
--ignore-revs-file. An empty file name resets the list. Config
options are parsed before the command line options.
- Rebased to master
- Added regression tests
v1 -> v2
v1: https://public-inbox.org/git/20190107213013.231514-1-brho@google.com/
- extracted the skiplist from fsck to avoid duplicating code
- overhauled the interface and options
- split out markIgnoredFiles
- handled merges
Barret Rhoden (6):
Move init_skiplist() outside of fsck
blame: use a helper function in blame_chunk()
blame: optionally track the line starts during fill_blame_origin()
blame: add the ability to ignore commits and their changes
blame: add a config option to mark ignored lines
RFC blame: use a fingerprint heuristic to match ignored lines
Documentation/blame-options.txt | 16 ++
Documentation/config/blame.txt | 11 +
Documentation/git-blame.txt | 1 +
blame.c | 384 +++++++++++++++++++++++++++-----
blame.h | 6 +
builtin/blame.c | 51 +++++
fsck.c | 37 +--
oidset.c | 35 +++
oidset.h | 8 +
t/t5504-fetch-receive-strict.sh | 14 +-
t/t8013-blame-ignore-revs.sh | 201 +++++++++++++++++
11 files changed, 665 insertions(+), 99 deletions(-)
create mode 100755 t/t8013-blame-ignore-revs.sh
--
2.21.0.392.gf8f6787159e-goog
next reply other threads:[~2019-04-03 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 16:02 Barret Rhoden [this message]
2019-04-03 16:02 ` [PATCH v5 1/6] Move init_skiplist() outside of fsck Barret Rhoden
2019-04-03 16:02 ` [PATCH v5 2/6] blame: use a helper function in blame_chunk() Barret Rhoden
2019-04-03 16:02 ` [PATCH v5 3/6] blame: optionally track the line starts during fill_blame_origin() Barret Rhoden
2019-04-03 16:02 ` [PATCH v5 4/6] blame: add the ability to ignore commits and their changes Barret Rhoden
2019-04-03 16:02 ` [PATCH v5 5/6] blame: add a config option to mark ignored lines Barret Rhoden
2019-04-03 16:02 ` [PATCH v5 6/6] RFC blame: use a fingerprint heuristic to match " Barret Rhoden
2019-04-04 16:37 ` SZEDER Gábor
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=20190403160207.149174-1-brho@google.com \
--to=brho@google.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
--cc=michael@platin.gs \
--cc=peff@peff.net \
--cc=stefanbeller@gmail.com \
--cc=whydoubt@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 public 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).