From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: What's cooking in git.git (Jan 2018, #04; Wed, 31)
Date: Fri, 02 Feb 2018 10:09:24 -0800 [thread overview]
Message-ID: <xmqq4lmzqn57.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <87mv0tm0l7.fsf@evledraar.booking.com> ("Ævar Arnfjörð Bjarmason"'s message of "Thu, 01 Feb 2018 12:05:40 +0100")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> On Thu, Feb 01 2018, Junio C. Hamano jotted:
>
>> * ab/wildmatch-tests (2018-01-30) 10 commits
> The 2018-01-30 series is the update mentioned in
> 87vaga9mgf.fsf@evledraar.gmail.com. You probably noticed this / just
> didn't adjust the note since you queued in in pu already, but just in
> case: the known issues in it have been resolved, but hopefully Johannes
> Schindelin can test it on Windows & report.
Thanks for a correction. Very much appreciated. Let's start moving
this forward then.
>> * ab/sha1dc-build (2017-12-12) 4 commits
>> . Makefile: use the sha1collisiondetection submodule by default
>> - sha1dc_git.h: re-arrange an ifdef chain for a subsequent change
>> - Makefile: under "make dist", include the sha1collisiondetection submodule
>> - Makefile: don't error out under DC_SHA1_EXTERNAL if DC_SHA1_SUBMODULE=auto
> Do you want to peel of 4/4 and just keep 1-3 should I submit another
> version without 4/4?
Nah, let's just discard the tip one without prejudice and move the
remainder forward.
Thanks.
next prev parent reply other threads:[~2018-02-02 18:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 0:56 What's cooking in git.git (Jan 2018, #04; Wed, 31) Junio C Hamano
2018-02-01 11:05 ` Ævar Arnfjörð Bjarmason
2018-02-02 18:09 ` Junio C Hamano [this message]
2018-02-09 17:06 ` Johannes Schindelin
2018-02-09 18:30 ` Ævar Arnfjörð Bjarmason
2018-02-01 12:11 ` Ævar Arnfjörð Bjarmason
2018-02-02 18:05 ` Junio C Hamano
2018-02-02 19:29 ` Ævar Arnfjörð Bjarmason
2018-02-09 18:37 ` Ævar Arnfjörð Bjarmason
2018-02-09 18:54 ` Junio C Hamano
2018-02-09 21:04 ` [PATCH 0/2] update-index doc: note new caveats in 2.17 Ævar Arnfjörð Bjarmason
2018-02-09 21:40 ` Junio C Hamano
2018-02-09 22:10 ` Ævar Arnfjörð Bjarmason
2018-02-09 21:04 ` [PATCH 1/2] update-index doc: note a fixed bug in the untracked cache Ævar Arnfjörð Bjarmason
2018-02-09 21:52 ` Junio C Hamano
2018-02-09 22:14 ` Ævar Arnfjörð Bjarmason
2018-02-09 22:50 ` Junio C Hamano
2018-02-09 22:58 ` Ævar Arnfjörð Bjarmason
2018-02-09 21:04 ` [PATCH 2/2] update-index doc: note the caveat with "could not open..." Ævar Arnfjörð Bjarmason
2018-02-10 10:09 ` What's cooking in git.git (Jan 2018, #04; Wed, 31) Duy Nguyen
2018-02-11 14:44 ` Ævar Arnfjörð Bjarmason
2018-02-12 10:04 ` Duy Nguyen
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=xmqq4lmzqn57.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
/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).