From: Ravi Mistry <rmistry@google.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, gitgitgadget@gmail.com,
abhijeet040403@gmail.com, code@khaugsbakk.name,
phillip.wood@dunelm.org.uk, sunshine@sunshineco.com,
rmistry@google.com
Subject: Re: [PATCH v2 2/2] blame: ignore revs in HEAD:.git-blame-ignore-revs
Date: Sat, 10 Oct 2026 18:40:07 +0000 [thread overview]
Message-ID: <20261010184007.112258-1-rmistry@google.com> (raw)
In-Reply-To: <xmqqbj92ochm.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> These Helped-by: drew my attention as none of these folks commented
> on v1 of this series. I do see they have helped the original series
> <pull.1809.v2.git.1728707867.gitgitgadget@gmail.com>, but it is not
> clear how much their inputs have survivied to this version.
From that earlier thread, Phillip suggested explaining why commit
ae3f36dea1 originally avoided a default file, Kristoffer suggested the
config override model and documenting --no-ignore-revs-file, and as
Eric noted, his comments were minor structural suggestions such as
updating the docs and placing the tests in t8013.
> > + while (!strbuf_getline(&sb, fp))
> > + parse_oidset_line(set, &sb, algop, fn, cbdata);
> > if (ferror(fp))
> > die_errno("Could not read '%s'", path);
> > fclose(fp);
> > strbuf_release(&sb);
> > }
>
> Shouldn't the above refactoring have been part of the previous step
> instead?
I extracted parse_oidset_line() in patch 2/2 because that is where the
second caller (oidset_parse_buffer_carefully()) was added, though
extracting it in patch 1/2 would avoid touching that loop in both
patches. Happy to move this into patch 1/2 if preferred.
Thanks!
next prev parent reply other threads:[~2026-10-10 18:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 23:29 [PATCH] blame: default to ignoring revisions in .git-blame-ignore-revs Ravi Mistry via GitGitGadget
2026-09-30 14:59 ` Ravi Mistry
2026-10-05 15:37 ` Junio C Hamano
2026-10-05 21:12 ` Ravi Mistry
2026-10-07 17:43 ` Junio C Hamano
2026-10-07 18:07 ` Ravi Mistry
2026-10-08 21:07 ` [PATCH v2 0/2] blame: ignore revs in HEAD:.git-blame-ignore-revs by default Ravi Mistry via GitGitGadget
2026-10-08 21:07 ` [PATCH v2 1/2] blame: harden ignore-revs parser and tag peeling Ravi Mistry via GitGitGadget
2026-10-09 5:07 ` Junio C Hamano
2026-10-10 19:25 ` Ravi Mistry
2026-10-08 21:07 ` [PATCH v2 2/2] blame: ignore revs in HEAD:.git-blame-ignore-revs Ravi Mistry via GitGitGadget
2026-10-09 20:17 ` Junio C Hamano
2026-10-10 6:12 ` Eric Sunshine
2026-10-10 18:40 ` Ravi Mistry [this message]
2026-10-11 18:58 ` Junio C Hamano
2026-10-11 22:29 ` Ravi Mistry
2026-10-11 23:07 ` Junio C Hamano
2026-10-12 9:13 ` Phillip Wood
2026-10-12 16:38 ` Junio C Hamano
2026-10-12 19:21 ` Ravi Mistry
2026-10-12 21:13 ` Junio C Hamano
2026-10-11 22:21 ` [PATCH v3 0/2] blame: ignore revs in HEAD:.git-blame-ignore-revs by default Ravi Mistry via GitGitGadget
2026-10-11 22:21 ` [PATCH v3 1/2] blame: harden ignore-revs parser and tag peeling Ravi Mistry via GitGitGadget
2026-10-11 22:21 ` [PATCH v3 2/2] blame: ignore revs in HEAD:.git-blame-ignore-revs Ravi Mistry via GitGitGadget
2026-10-12 9:10 ` Phillip Wood
2026-10-12 15:48 ` Ravi Mistry
2026-10-12 19:17 ` [PATCH v4 0/2] blame: ignore revs in HEAD:.git-blame-ignore-revs by default Ravi Mistry via GitGitGadget
2026-10-12 19:17 ` [PATCH v4 1/2] blame: harden ignore-revs parser and tag peeling Ravi Mistry via GitGitGadget
2026-10-12 19:17 ` [PATCH v4 2/2] blame: ignore revs in HEAD:.git-blame-ignore-revs Ravi Mistry via GitGitGadget
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261010184007.112258-1-rmistry@google.com \
--to=rmistry@google.com \
--cc=abhijeet040403@gmail.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=sunshine@sunshineco.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.