Git development
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Justin Tobler <jltobler@gmail.com>
Subject: Re: [PATCH v2 0/4] odb: eagerly load alternates
Date: Thu, 13 Aug 2026 10:56:17 +0200	[thread overview]
Message-ID: <an2Gsf0LzYRKkQkZ@pks.im> (raw)
In-Reply-To: <xmqqy0ebxsap.fsf@gitster.g>

On Wed, Aug 12, 2026 at 08:38:38AM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
> 
> > The series is built on top of 010afd3166 (The 12th batch, 2026-08-07)
> > with ps/odb-make-creation-pluggable at e927cfeb21 (odb: make creation of
> > on-disk structures pluggable, 2026-08-07) merged into it.
> 
> It is not a clean merge, though.  Please double check the
> synthesized base when I push the integration results out later
> today.  d296c52baa (Merge branch 'ps/odb-make-creation-pluggable'
> into ps/odb-eagerly-load-alternates, 2026-08-12) will be the merge,
> unless I notice and fix a mismerge in it before I push it out.

Hm. I'm probably missing something, but your merge is a bit curious as
you merge the dependency into the feature branch instead of making it
the base of it. If I do the following:

    # Switch to the master commit.
    $ git switch --detach 010afd3166
    # Merge the dependnecy.
    $ git merge e927cfeb21

Then the only merge conflict I get is in "odb/source-files.c". This is a
trivial merge conflict though, as it only impacts included headers. And
then the rest of this series applies on top of that merge base without
any further issues.

Am I missing something?

Thanks!

Patrick

  reply	other threads:[~2026-08-13  8:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 13:33 [PATCH 0/4] odb: eagerly load alternates Patrick Steinhardt
2026-08-10 13:33 ` [PATCH 1/4] odb: decouple source path comparisons from `the_repository` Patrick Steinhardt
2026-08-11 22:04   ` Justin Tobler
2026-08-12  5:39     ` Patrick Steinhardt
2026-08-10 13:33 ` [PATCH 2/4] odb: eagerly initialize alternates Patrick Steinhardt
2026-08-11 22:15   ` Justin Tobler
2026-08-12  5:39     ` Patrick Steinhardt
2026-08-10 13:33 ` [PATCH 3/4] odb: drop `loaded_alternates` field Patrick Steinhardt
2026-08-11 22:22   ` Justin Tobler
2026-08-10 13:33 ` [PATCH 4/4] odb: drop `alternates_db` field Patrick Steinhardt
2026-08-11 22:31   ` Justin Tobler
2026-08-12  5:39     ` Patrick Steinhardt
2026-08-12  9:13 ` [PATCH v2 0/4] odb: eagerly load alternates Patrick Steinhardt
2026-08-12  9:13   ` [PATCH v2 1/4] odb: decouple source path comparisons from `the_repository` Patrick Steinhardt
2026-08-13 12:23     ` Karthik Nayak
2026-08-13 13:17       ` Patrick Steinhardt
2026-08-12  9:13   ` [PATCH v2 2/4] odb: eagerly initialize alternates Patrick Steinhardt
2026-08-12  9:13   ` [PATCH v2 3/4] odb: drop `loaded_alternates` field Patrick Steinhardt
2026-08-13 12:25     ` Karthik Nayak
2026-08-12  9:14   ` [PATCH v2 4/4] odb: drop `alternates_db` field Patrick Steinhardt
2026-08-12 15:38   ` [PATCH v2 0/4] odb: eagerly load alternates Junio C Hamano
2026-08-13  8:56     ` Patrick Steinhardt [this message]
2026-08-13 12:28   ` Karthik Nayak
2026-08-13 17:09   ` Justin Tobler

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=an2Gsf0LzYRKkQkZ@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jltobler@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox