From: "René Scharfe" <l.s.r@web.de>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, 天几 <muzimuzhi@gmail.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Dongcan Jiang" <dongcan.jiang@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH 2/1] pull: remove --update-head-ok from documentation
Date: Wed, 1 Apr 2020 01:21:29 +0200 [thread overview]
Message-ID: <82876e28-ede5-ad1b-856e-e2267268e7c7@web.de> (raw)
In-Reply-To: <20200331214851.GB95875@syl.local>
Am 31.03.20 um 23:48 schrieb Taylor Blau:
> This patch (and the other one attached to this thread) both look good.
> However, the numbering on this patch is a little weird, (2/1? 3/1?). Is
> there a third patch missing, and/or are your subject lines mangled?
>
> Please share if there is more, or if I should be interpreting this
> series differently. Otherwise this patch makes sense.
The first patch was
https://lore.kernel.org/git/a406c273-9a2c-72ed-c5e3-4c19848f0f94@web.de/
and I meant to only send that one. A few weeks later I couldn't help
but follow up with two more patches. I don't plan to continue the
series any further.
René
next prev parent reply other threads:[~2020-03-31 23:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 19:17 Documented option "--deepen" is unknown to git-pull 天几
2020-03-09 21:51 ` René Scharfe
2020-03-28 14:48 ` [PATCH 2/1] pull: remove --update-head-ok from documentation René Scharfe
2020-03-31 21:48 ` Taylor Blau
2020-03-31 23:21 ` René Scharfe [this message]
2020-03-28 14:48 ` [PATCH 3/1] pull: pass documented fetch options on René Scharfe
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=82876e28-ede5-ad1b-856e-e2267268e7c7@web.de \
--to=l.s.r@web.de \
--cc=dongcan.jiang@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=muzimuzhi@gmail.com \
--cc=pclouds@gmail.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).