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 0/5] Tweak the 2.4.0 release notes and related docs
Date: Thu, 23 Apr 2015 14:27:45 +0200 [thread overview]
Message-ID: <1429792070-22991-1-git-send-email-mhagger@alum.mit.edu> (raw)
Patches 1 and 2 add some manpage documentation for features mentioned
in the release notes that were not adequately documented.
Patches 3 and 4 correct a couple of concrete problems in the release
notes.
Patch 5 is a smörgåsbord of suggested stylistic changes to the release
notes. Feel free to pick and choose the ones that you think are
improvements.
Michael Haggerty (5):
status: document the -v/--verbose option
git tag: mention versionsort.prereleaseSuffix in manpage
RelNotes: correct name of versionsort.prereleaseSuffix
RelNotes: refer to the rebase -i "todo list", not "insn sheet"
RelNotes: wordsmithing
Documentation/RelNotes/2.4.0.txt | 338 ++++++++++++++++++++-------------------
Documentation/git-status.txt | 9 ++
Documentation/git-tag.txt | 11 +-
3 files changed, 189 insertions(+), 169 deletions(-)
--
2.1.4
next 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 Michael Haggerty [this message]
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 ` [PATCH 3/5] RelNotes: correct name of versionsort.prereleaseSuffix Michael Haggerty
2015-04-23 18:29 ` 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-1-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).