All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/7] builtin/commit-graph: some small cleanups
Date: Wed, 28 Oct 2026 13:40:39 -0700	[thread overview]
Message-ID: <xmqqv76l7e48.fsf@gitster.g> (raw)
In-Reply-To: <20261028-pks-commit-graph-cleanups-v1-0-c549344c363f@pks.im> (Patrick Steinhardt's message of "Wed, 28 Oct 2026 12:57:52 +0100")

Patrick Steinhardt <ps@pks.im> writes:

> Hi,
>
> I'm working into the direction of making commit-graphs pluggable so that
> backends can fully control where exactly commit-graphs are written to
> and read from. This patch series contains a couple of small preliminary
> cleanups.
>
> Most of the patches are rather uncontroversial, I'd assume. The only
> one that might raise some eyebrows is where I "fix" git-commit-graph(1)
> to only accept "--object-directory=" for subcommands instead of both as
> a command-global and subcommand option. I feel like this is quite a weird
> outlier, and it got in my way. In any case, I'd appreciate some extra
> thoughts on this.
>
> Thanks!
>
> Patrick

I read the first 4 steps and they all looked sensible.  May come
back to the remainder later this week if nobody beats me to it.

Thanks.

>
> ---
> Patrick Steinhardt (7):
>       builtin/commit-graph: rename subcommand functions
>       builtin/commit-graph: drop declaration for `read_replace_refs`
>       builtin/commit-graph: get rid of `the_repository`
>       builtin/commit-graph: drop global "--object-dir=" switch
>       builtin/commit-graph: simplify how we wire up common options
>       builtin/commit-graph: de-globalize write options handling
>       builtin/commit-graph: de-globalize options handling
>
>  builtin/commit-graph.c | 131 +++++++++++++++++++++++++------------------------
>  1 file changed, 67 insertions(+), 64 deletions(-)
>
>
> ---
> base-commit: 37b3475fb530c14109211faca33716a173db61ed
> change-id: 20261028-pks-commit-graph-cleanups-d1dc30f3e05a

  parent reply	other threads:[~2026-10-28 20:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 11:57 [PATCH 0/7] builtin/commit-graph: some small cleanups Patrick Steinhardt
2026-10-28 11:57 ` [PATCH 1/7] builtin/commit-graph: rename subcommand functions Patrick Steinhardt
2026-10-28 11:57 ` [PATCH 2/7] builtin/commit-graph: drop declaration for `read_replace_refs` Patrick Steinhardt
2026-10-28 11:57 ` [PATCH 3/7] builtin/commit-graph: get rid of `the_repository` Patrick Steinhardt
2026-10-28 11:57 ` [PATCH 4/7] builtin/commit-graph: drop global "--object-dir=" switch Patrick Steinhardt
2026-10-28 11:57 ` [PATCH 5/7] builtin/commit-graph: simplify how we wire up common options Patrick Steinhardt
2026-10-28 11:57 ` [PATCH 6/7] builtin/commit-graph: de-globalize write options handling Patrick Steinhardt
2026-10-28 11:57 ` [PATCH 7/7] builtin/commit-graph: de-globalize " Patrick Steinhardt
2026-10-28 17:13   ` Mark C. Chu-Carroll
2026-10-28 20:40 ` Junio C Hamano [this message]
2026-10-28 21:28   ` [PATCH 0/7] builtin/commit-graph: some small cleanups Junio C Hamano

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=xmqqv76l7e48.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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.