From: Junio C Hamano <gitster@pobox•com>
To: Jonathan Nieder <jrnieder@gmail•com>
Cc: git@vger•kernel.org, Jonathan Tan <jonathantanmy@google•com>
Subject: Re: [PATCH] fetch doc: src side of refspec could be full SHA-1
Date: Wed, 18 Oct 2017 06:00:17 +0900 [thread overview]
Message-ID: <xmqqwp3tmqvy.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171017193511.szbmrclju22a6p5l@aiede.mtv.corp.google.com> (Jonathan Nieder's message of "Tue, 17 Oct 2017 12:35:11 -0700")
Jonathan Nieder <jrnieder@gmail•com> writes:
> nits:
>
> s/most typically/typically/
> s/an fully/a fully/
>
> With those tweaks,
> Reviewed-by: Jonathan Nieder <jrnieder@gmail•com>
Thanks.
prev parent reply other threads:[~2017-10-17 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 3:56 [PATCH] fetch doc: src side of refspec could be full SHA-1 Junio C Hamano
2017-10-17 19:35 ` Jonathan Nieder
2017-10-17 21:00 ` Junio C Hamano [this message]
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=xmqqwp3tmqvy.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jonathantanmy@google$(echo .)com \
--cc=jrnieder@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