git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>,  git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2023, #04; Thu, 9)
Date: Fri, 10 Nov 2023 08:33:49 +0900	[thread overview]
Message-ID: <xmqqpm0iy00y.fsf@gitster.g> (raw)
In-Reply-To: <ZUzcmsfJe6jk4fTk@nand.local> (Taylor Blau's message of "Thu, 9 Nov 2023 08:20:26 -0500")

Taylor Blau <me@ttaylorr.com> writes:

> On Thu, Nov 09, 2023 at 02:40:28AM +0900, Junio C Hamano wrote:
>> * tb/merge-tree-write-pack (2023-10-23) 5 commits
> ...
> This series received a couple of LGTMs from you and Patrick:
>
>   - https://lore.kernel.org/git/xmqqo7go7w63.fsf@gitster.g/#t
>   - https://lore.kernel.org/git/ZTjKmcV5c_EFuoGo@tanuki/

Yup, I am aware of them.

> Johannes had posted some comments[1] about instead using a temporary
> object store where objects are written as loose that would extend to git
> replay....

I was hoping to hear from Johannes saying he agrees with the above.
It is not strictly required, but is much nice to have once we hear
"let's step back a bit---are we going in the right direction?" and
it has been responded.

Thanks.


  reply	other threads:[~2023-11-09 23:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 17:40 What's cooking in git.git (Nov 2023, #04; Thu, 9) Junio C Hamano
2023-11-09  7:50 ` Jeff King
2023-11-09 13:15   ` Taylor Blau
2023-11-09 13:20 ` Taylor Blau
2023-11-09 23:33   ` Junio C Hamano [this message]
2023-11-15 12:57     ` tb/merge-tree-write-pack, was " Johannes Schindelin
2023-11-16 20:17       ` Jeff King
2023-11-11  0:00   ` tb/merge-tree-write-pack [Was: Re: What's cooking in git.git (Nov 2023, #04; Thu, 9)] Elijah Newren

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=xmqqpm0iy00y.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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).