All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2022, #03; Mon, 11)
Date: Wed, 13 Jul 2022 09:31:30 -0700	[thread overview]
Message-ID: <xmqq4jzldlel.fsf@gitster.g> (raw)
In-Reply-To: <dfe0c1ab-33f8-f13e-71ce-1829bb0d2d7f@iee.email> (Philip Oakley's message of "Tue, 12 Jul 2022 23:29:21 +0100")

Philip Oakley <philipoakley@iee.email> writes:

> I'm expecting to do a re-roll for both these, though I'm just recovering
> from an infection.
> If you could hold off for a few days that would be great.

Be well soon and take care of yourself.

Thanks, will relabel them to "Expecting a reroll".

  reply	other threads:[~2022-07-13 16:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 17:07 What's cooking in git.git (Jul 2022, #03; Mon, 11) Junio C Hamano
2022-07-12 22:19 ` gc/bare-repo-discovery (was Re: What's cooking in git.git (Jul 2022, #03; Mon, 11)) Glen Choo
2022-07-13 16:29   ` Junio C Hamano
2022-07-14 16:17     ` Johannes Schindelin
2022-07-14 18:27       ` Junio C Hamano
2022-07-12 22:29 ` What's cooking in git.git (Jul 2022, #03; Mon, 11) Philip Oakley
2022-07-13 16:31   ` Junio C Hamano [this message]
2022-07-12 23:28 ` ac/bitmap-lookup-table (was: Re: What's cooking in git.git (Jul 2022, #03; Mon, 11)) Taylor Blau
2022-07-13 16:42   ` ac/bitmap-lookup-table Junio C Hamano
2022-07-13 11:10 ` js/bisect-in-c, was Re: What's cooking in git.git (Jul 2022, #03; Mon, 11) Johannes Schindelin
2022-07-13 11:18   ` Ævar Arnfjörð Bjarmason
2022-07-13 16:01     ` Junio C Hamano
2022-07-14  0:22       ` Ævar Arnfjörð Bjarmason
2022-07-14 19:35       ` Johannes Schindelin
2022-07-14 21:09         ` Ævar Arnfjörð Bjarmason
2022-08-16  8:51           ` Johannes Schindelin
2022-08-17  0:49             ` Ævar Arnfjörð Bjarmason

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=xmqq4jzldlel.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=philipoakley@iee.email \
    /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.