git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Jeff King <peff@peff.net>,
	Eric Wong <e@80x24.org>
Subject: Re: What's cooking in git.git (Apr 2021, #05; Mon, 19)
Date: Tue, 20 Apr 2021 23:14:06 +0000	[thread overview]
Message-ID: <YH9gPt410QBRjG59@camp.crustytoothpaste.net> (raw)
In-Reply-To: <87mttt2hcu.fsf@evledraar.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]

On 2021-04-20 at 13:52:33, Ævar Arnfjörð Bjarmason wrote:
> This has a textual conflict (no longer a semantic one) with the above
> ab/unexpected-object-type etc.
> 
> As noted in
> https://lore.kernel.org/git/87mttx121j.fsf@evledraar.gmail.com/ I had
> questions about the approach in hash-object.c, in particular I have
> POC/WIP patches that make one of brian's TODO tests pass, by doing the
> "we are in SHA256 mode" earlier, which is also less code as we won't
> need to add special handling to a large part of hash-object.c (or, in
> the future, other such commands).

I'm going to drop those first two patches for now, since I plan to
implement them in a different way in the future.
-- 
brian m. carlson (he/him or they/them)
Houston, Texas, US

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  parent reply	other threads:[~2021-04-20 23:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 23:25 Junio C Hamano
2021-04-20 13:23 ` Matheus Tavares Bernardino
2021-04-20 13:52 ` Ævar Arnfjörð Bjarmason
2021-04-20 22:15   ` Junio C Hamano
2021-04-20 23:14   ` brian m. carlson [this message]
2021-04-21  8:26     ` Ævar Arnfjörð Bjarmason
2021-04-21 22:32       ` brian m. carlson
2021-04-20 23:51   ` Junio C Hamano
2021-04-23 14:41   ` Jeff King
2021-04-20 14:28 ` Jeff Hostetler

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=YH9gPt410QBRjG59@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=avarab@gmail.com \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --subject='Re: What'\''s cooking in git.git (Apr 2021, #05; Mon, 19)' \
    /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

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 NNTP newsgroup(s).