From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Michael Haggerty <mhagger@alum.mit.edu>
Subject: [PATCH 3/5] RelNotes: correct name of versionsort.prereleaseSuffix
Date: Thu, 23 Apr 2015 14:27:48 +0200 [thread overview]
Message-ID: <1429792070-22991-4-git-send-email-mhagger@alum.mit.edu> (raw)
In-Reply-To: <1429792070-22991-1-git-send-email-mhagger@alum.mit.edu>
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
---
Documentation/RelNotes/2.4.0.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/RelNotes/2.4.0.txt b/Documentation/RelNotes/2.4.0.txt
index a0ee37d..c02de8d 100644
--- a/Documentation/RelNotes/2.4.0.txt
+++ b/Documentation/RelNotes/2.4.0.txt
@@ -109,8 +109,8 @@ UI, Workflows & Features
"cd ''" which silently behaves as a no-op.
(merge 6a536e2 kn/git-cd-to-empty later to maint).
- * The versionsort.prerelease configuration variable can be used to
- specify that v1.0-pre1 comes before v1.0.
+ * The versionsort.prereleaseSuffix configuration variable can be used
+ to specify that v1.0-pre1 comes before v1.0.
* A new "push.followTags" configuration turns the "--follow-tags"
option on by default for the "git push" command.
--
2.1.4
next prev parent reply other threads:[~2015-04-23 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 12:27 [PATCH 0/5] Tweak the 2.4.0 release notes and related docs Michael Haggerty
2015-04-23 12:27 ` [PATCH 1/5] status: document the -v/--verbose option Michael Haggerty
2015-04-23 18:26 ` Junio C Hamano
2015-04-23 12:27 ` [PATCH 2/5] git tag: mention versionsort.prereleaseSuffix in manpage Michael Haggerty
2015-04-23 18:28 ` Junio C Hamano
2015-04-23 12:27 ` Michael Haggerty [this message]
2015-04-23 18:29 ` [PATCH 3/5] RelNotes: correct name of versionsort.prereleaseSuffix Junio C Hamano
2015-04-23 12:27 ` [PATCH 4/5] RelNotes: refer to the rebase -i "todo list", not "insn sheet" Michael Haggerty
2015-04-23 12:27 ` [PATCH 5/5] RelNotes: wordsmithing Michael Haggerty
2015-04-23 12:47 ` Michael Haggerty
2015-04-23 15:38 ` 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=1429792070-22991-4-git-send-email-mhagger@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).