git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2021, #03; Thu, 20)
Date: Mon, 24 May 2021 12:29:16 +0200	[thread overview]
Message-ID: <87lf84o23t.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <60a8352c936aa_55d9020873@natae.notmuch>


On Fri, May 21 2021, Felipe Contreras wrote:

> Junio C Hamano wrote:
>> Here are the topics that have been cooking.
>
>> --------------------------------------------------
>> [New Topics]
>
> Is this not a topic?
>
> 1. doc: asciidoc cleanups
> https://lore.kernel.org/git/20210514115631.503276-1-felipe.contreras@gmail.com/
>
> Or this?
>
> 2. doc: asciidoctor: direct man page creation and fixes
> https://lore.kernel.org/git/20210514121435.504423-1-felipe.contreras@gmail.com/
>
> How about this?
>
> 3. doc: cleanup old cruft and asciidoctor revamp
> https://lore.kernel.org/git/20210515115653.922902-1-felipe.contreras@gmail.com/
>
> Granted, they step into one another, but at least #1 is more than ready
> to be merged.
>
> I'm sending new versions of all of those.

These were sent around the same time as v2.32.0-rc0 went out. Junio
tends to not pick up new things around the release freeze. I've only
skimmed those topics but they seem like sensible fixes, I think it's
probably best to let discussion on them settle/continue, and re-roll or
re-send sometime after v2.32.0.

  reply	other threads:[~2021-05-24 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20  3:26 What's cooking in git.git (May 2021, #03; Thu, 20) Junio C Hamano
2021-05-20  8:18 ` Elijah Newren
2021-05-20 22:43   ` Junio C Hamano
2021-05-20 11:25 ` Ævar Arnfjörð Bjarmason
2021-05-21 22:33 ` Felipe Contreras
2021-05-24 10:29   ` Ævar Arnfjörð Bjarmason [this message]
2021-05-24 16:48     ` Felipe Contreras

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=87lf84o23t.fsf@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).