From: Junio C Hamano <gitster@pobox.com>
To: Nathan PAYRE <second.payre@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
daniel.bensoussan--bohm@etu.univ-lyon1.fr,
timothee.albertin@etu.univ-lyon1.fr,
"Robert P. J. Day" <rpjday@crashcourse.ca>,
matthieu.moy@univ-lyon1.fr,
PAYRE NATHAN p1508475 <nathan.payre@etu.univ-lyon1.fr>
Subject: Re: [PATCH] Documentation/git-config.txt: reword missleading sentence
Date: Tue, 10 Oct 2017 17:48:08 +0900 [thread overview]
Message-ID: <xmqqtvz7pewn.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGb4CBUaQJOskTiXm0w+3V7E8kkaA5EiG1w0s39WDCVH-5AVoA@mail.gmail.com> (Nathan PAYRE's message of "Tue, 10 Oct 2017 10:19:59 +0200")
Nathan PAYRE <second.payre@gmail.com> writes:
> Thanks you for the this complete answer,
> we take note of your comments.
>
> We would like to reword something else in the same line
> and we don't know what is the best way to do that properly.
> Should we do a [PATCH v2] or revert the last commit and
> commit a new one?
I'd imagine that it is in the same spirit of the old one
(i.e. "let's make it less confusing"), so let's have a single patch
that has both changes which is [PATCH v2].
Thanks.
next prev parent reply other threads:[~2017-10-10 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 8:17 [PATCH] Documentation/git-config.txt: reword missleading sentence PAYRE NATHAN p1508475
2017-10-05 10:13 ` Junio C Hamano
2017-10-10 8:19 ` Nathan PAYRE
2017-10-10 8:48 ` Junio C Hamano [this message]
2017-10-12 9:17 ` [PATCH v2] " second.payre
2017-10-13 0:23 ` Junio C Hamano
2017-10-13 8:32 ` Moy Matthieu
2017-10-13 12:04 ` Junio C Hamano
2017-10-18 20:27 ` [PATCH v3] " PAYRE NATHAN p1508475
2017-10-18 22:12 ` Jonathan Nieder
2017-10-19 4:58 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtvz7pewn.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=daniel.bensoussan--bohm@etu.univ-lyon1.fr \
--cc=git@vger.kernel.org \
--cc=matthieu.moy@univ-lyon1.fr \
--cc=nathan.payre@etu.univ-lyon1.fr \
--cc=rpjday@crashcourse.ca \
--cc=second.payre@gmail.com \
--cc=timothee.albertin@etu.univ-lyon1.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).