From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Emily Shaffer <emilyshaffer@google.com>,
Jeff King <peff@peff.net>, Han-Wen Nienhuys <hanwen@google.com>,
Jonathan Tan <jonathantanmy@google.com>,
Andrei Rybak <rybak.a.v@gmail.com>
Subject: Re: What's cooking in git.git (Jul 2021, #02; Thu, 8)
Date: Wed, 21 Jul 2021 11:15:11 -0700 [thread overview]
Message-ID: <xmqqsg07cz4g.fsf@gitster.g> (raw)
In-Reply-To: <87tul24iw2.fsf@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Sat, 10 Jul 2021 10:56:19 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>> * ab/serve-cleanup (2021-06-28) 8 commits
>> - upload-pack.c: convert to new serve.c "startup" config cb
>> ...
> I have a re-roll of this queued locally. It seemed people were on the
> fence about the whole "startup config" thing so I initially planned to
> just drop it, but then I started fixing some other related serve.c code
> and found a good/better use for it, so maybe I'll keep it. Will post it
> soon.
>
> FWIW Han-Wen's "let's rename the serve() function" suggestion sent me on
> an Odyssey of discovering various unused/overly-complex-for-no-reason
> code around protcol v1/v2 that I think we should just clean up...
I do not think the startup config thing got much traction, either,
but in any case did I miss an update for this one?
Thanks.
prev parent reply other threads:[~2021-07-21 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 22:28 What's cooking in git.git (Jul 2021, #02; Thu, 8) Junio C Hamano
2021-07-09 0:48 ` brian m. carlson
2021-07-09 14:54 ` Junio C Hamano
2021-07-09 1:25 ` Elijah Newren
2021-07-10 8:56 ` Ævar Arnfjörð Bjarmason
2021-07-21 18:15 ` Junio C Hamano [this message]
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=xmqqsg07cz4g.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=hanwen@google.com \
--cc=jonathantanmy@google.com \
--cc=peff@peff.net \
--cc=rybak.a.v@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 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.