From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Han-Wen Nienhuys <hanwen@google.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH 0/6] Minimal patch series to fix the CI runs of hn/reftable
Date: Mon, 04 May 2020 08:56:33 -0700 [thread overview]
Message-ID: <xmqq8si7ithq.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <pull.623.git.1588599086.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Mon, 04 May 2020 13:31:20 +0000")
"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:
> These patches are not intended to be complete, not by any stretch of
> imagination. They are just enough to get the CI run to pass, even in the
> Windows-specific parts.
Thanks. Now I know at least somebody has been paying attention to
call for help in the past few issues of the "What's cooking" report ;-)
next prev parent reply other threads:[~2020-05-04 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 13:31 [PATCH 0/6] Minimal patch series to fix the CI runs of hn/reftable Johannes Schindelin via GitGitGadget
2020-05-04 13:31 ` [PATCH 1/6] fixup! Add reftable library Johannes Schindelin via GitGitGadget
2020-05-04 13:31 ` [PATCH 2/6] " Johannes Schindelin via GitGitGadget
2020-05-04 13:31 ` [PATCH 3/6] " Johannes Schindelin via GitGitGadget
2020-05-04 13:31 ` [PATCH 4/6] " Johannes Schindelin via GitGitGadget
2020-05-04 13:31 ` [PATCH 5/6] " Johannes Schindelin via GitGitGadget
2020-05-04 13:31 ` [PATCH 6/6] vcxproj: adjust for the reftable changes Johannes Schindelin via GitGitGadget
2020-05-04 17:12 ` Junio C Hamano
2020-05-04 15:56 ` Junio C Hamano [this message]
2020-05-05 8:02 ` [PATCH 0/6] Minimal patch series to fix the CI runs of hn/reftable Johannes Schindelin
2020-05-04 17:04 ` Han-Wen Nienhuys
2020-05-05 8:00 ` Johannes Schindelin
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=xmqq8si7ithq.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=hanwen@google.com \
--cc=johannes.schindelin@gmx.de \
/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.