From: Barret Rhoden <brho@google.com>
To: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2019, #06; Wed, 26)
Date: Mon, 1 Jul 2019 10:07:05 -0400 [thread overview]
Message-ID: <4d466fce-15df-3a73-f5f9-f29bc5b79a04@google.com> (raw)
In-Reply-To: <20190628062457.GA18662@sigill.intra.peff.net>
On 6/28/19 2:24 AM, Jeff King wrote:
> On Wed, Jun 26, 2019 at 03:29:29PM -0700, Junio C Hamano wrote:
>
>> * br/blame-ignore (2019-06-20) 9 commits
>> - blame: add a test to cover blame_coalesce()
>> - blame: use the fingerprint heuristic to match ignored lines
>> - blame: add a fingerprint heuristic to match ignored lines
>> - blame: optionally track line fingerprints during fill_blame_origin()
>> - blame: add config options for the output of ignored or unblamable lines
>> - blame: add the ability to ignore commits and their changes
>> - blame: use a helper function in blame_chunk()
>> - Move oidset_parse_file() to oidset.c
>> - fsck: rename and touch up init_skiplist()
>>
>> "git blame" learned to "ignore" commits in the history, whose
>> effects (as well as their presence) get ignored.
>>
>> Will merge to 'next'.
>> cf. <20190620163820.231316-1-brho@google.com> (v9)
>
> My -Wunused-parameter branch complained about merging with this. Since
> it's in 'next', we'd want something like this on top, I think (ideally
> after Barret confirms my hand-waving below).
Looks good to me.
Thanks,
Barret
>
> -- >8 --
> Subject: [PATCH] blame: drop some unused function parameters
>
> These unused parameters were introduced recently as part of the
> br/blame-ignore topic. I assume they are not indicative of bugs, but are
> just leftovers from the development process (they were introduced by the
> series but not used in any of its iterations).
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> blame.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/blame.c b/blame.c
> index 86f6b2bd33..acb1bf7f7a 100644
> --- a/blame.c
> +++ b/blame.c
> @@ -981,7 +981,7 @@ static int *fuzzy_find_matching_lines(struct blame_origin *parent,
> return result;
> }
>
> -static void fill_origin_fingerprints(struct blame_origin *o, mmfile_t *file)
> +static void fill_origin_fingerprints(struct blame_origin *o)
> {
> int *line_starts;
>
> @@ -1035,7 +1035,7 @@ static void fill_origin_blob(struct diff_options *opt,
> else
> *file = o->file;
> if (fill_fingerprints)
> - fill_origin_fingerprints(o, file);
> + fill_origin_fingerprints(o);
> }
>
> static void drop_origin_blob(struct blame_origin *o)
> @@ -1653,7 +1653,6 @@ static void guess_line_blames(struct blame_origin *parent,
> */
> static void ignore_blame_entry(struct blame_entry *e,
> struct blame_origin *parent,
> - struct blame_origin *target,
> struct blame_entry **diffp,
> struct blame_entry **ignoredp,
> struct blame_line_tracker *line_blames)
> @@ -1802,7 +1801,7 @@ static void blame_chunk(struct blame_entry ***dstq, struct blame_entry ***srcq,
> samep = n;
> }
> if (ignore_diffs) {
> - ignore_blame_entry(e, parent, target, &diffp, &ignoredp,
> + ignore_blame_entry(e, parent, &diffp, &ignoredp,
> line_blames + e->s_lno - tlno);
> } else {
> e->next = diffp;
>
next prev parent reply other threads:[~2019-07-01 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 22:29 What's cooking in git.git (Jun 2019, #06; Wed, 26) Junio C Hamano
2019-06-26 22:41 ` Jonathan Tan
2019-06-27 17:11 ` Junio C Hamano
2019-06-27 19:48 ` Matthew DeVore
2019-06-28 2:26 ` Junio C Hamano
2019-06-28 6:24 ` Jeff King
2019-07-01 14:07 ` Barret Rhoden [this message]
2019-07-01 16:29 ` Junio C Hamano
2019-07-01 17:55 ` Barret Rhoden
2019-06-28 19:11 ` Thomas Gummerer
2019-06-29 14:08 ` Phillip Wood
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=4d466fce-15df-3a73-f5f9-f29bc5b79a04@google.com \
--to=brho@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).