From: Denton Liu <liu.denton@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Andreas Heiduk <asheiduk@gmail.com>,
Duy Nguyen <pclouds@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v3 0/4] cleanup revisions.txt
Date: Sun, 5 May 2019 12:06:54 -0400 [thread overview]
Message-ID: <cover.1557072286.git.liu.denton@gmail.com> (raw)
In-Reply-To: <cover.1557071877.git.liu.denton@gmail.com>
Thanks again for the comments, Andreas! I've incorporated all of them
into this reroll.
---
Changes since v2:
* Marked more optional arguments with []
* Added Andreas' "revisions.txt: remove ambibuity between <rev>:<path>
and :<path>" patch
Changes since v1:
* Added patch to fix instances of "rev" to "<rev>"
* Marked all optional rev arguments with []
Andreas Heiduk (1):
revisions.txt: remove ambibuity between <rev>:<path> and :<path>
Denton Liu (3):
revisions.txt: change "rev" to "<rev>"
revisions.txt: mark optional rev arguments with []
revisions.txt: mention <rev>~ form
Documentation/revisions.txt | 29 ++++++++++++++---------------
1 file changed, 14 insertions(+), 15 deletions(-)
--
2.21.0.1049.geb646f7864
next parent reply other threads:[~2019-05-05 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1557071877.git.liu.denton@gmail.com>
2019-05-05 16:06 ` Denton Liu [this message]
2019-05-05 16:06 ` [PATCH v3 1/4] revisions.txt: change "rev" to "<rev>" Denton Liu
2019-05-05 16:07 ` [PATCH v3 2/4] revisions.txt: mark optional rev arguments with [] Denton Liu
2019-05-05 16:07 ` [PATCH v3 3/4] revisions.txt: mention <rev>~ form Denton Liu
2019-05-05 16:07 ` [PATCH v3 4/4] revisions.txt: remove ambibuity between <rev>:<path> and :<path> Denton Liu
2019-05-05 16:10 ` [PATCH v3 0/4] cleanup revisions.txt Denton Liu
2019-05-07 14:29 ` Denton Liu
2019-05-07 15:16 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1557072286.git.liu.denton@gmail.com \
--to=liu.denton@gmail.com \
--cc=asheiduk@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.