From: Junio C Hamano <gitster@pobox•com>
To: Elijah Newren <newren@gmail•com>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: What's cooking in git.git (Dec 2017, #05; Wed, 27)
Date: Thu, 28 Dec 2017 11:02:03 -0800 [thread overview]
Message-ID: <xmqqh8sallqs.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CABPp-BHxcFU+e4OgccWb+LgLbMo5sJsNjYFQb=WnxViTFdOu=g@mail.gmail.com> (Elijah Newren's message of "Wed, 27 Dec 2017 17:09:34 -0800")
Elijah Newren <newren@gmail•com> writes:
> surprised by the branch name, though. Was 'ew/' a typo,
Blush X-<. Yes it is a typo.
next prev parent reply other threads:[~2017-12-28 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 21:34 What's cooking in git.git (Dec 2017, #05; Wed, 27) Junio C Hamano
2017-12-28 1:09 ` Elijah Newren
2017-12-28 19:02 ` Junio C Hamano [this message]
2018-01-02 20:04 ` Stefan Beller
2018-01-02 22:19 ` Jonathan Nieder
2018-01-03 9:26 ` Daniel Knittl-Frank
2018-01-03 9:57 ` Kaartic Sivaraam
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=xmqqh8sallqs.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=newren@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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