From: Philip Oakley <philipoakley@iee.org>
To: GitList <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
=Stefan Nwe <stefan.naewe@atlas-elektronik.com>
Subject: [PATCH] Git release notes man page
Date: Sat, 15 Feb 2014 10:29:38 +0000 [thread overview]
Message-ID: <1392460179-776-1-git-send-email-philipoakley@iee.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 1159 bytes --]
A few days too late for the 1.9.0 release cycle :(
This responds to Stefan Näwe's request for a 'git help' command that would
access the release notes. ($gmane/240595 17 Jan 2014).
I've used the full name "release-notes" for the help guide rather than
Stefan's original 'git help relnotes'.
The release-notes man page lists just the notes for the current release.
The combined notes for all releases is nearing 15k lines.
The one formatting niggle is that the included text is column shifted
such that the the raw text now starts at col 12 for the man page and
reaches past col 80. Is there an attribute setting to not indent the
included block text within a man page? It looks fine in --web format.
I used the code.google link, rather than kernel.org, for the previous
release notes to match the link currently used in git(1).
Philip Oakley (1):
Provide a release-notes man page / guide
Documentation/Makefile | 1 +
Documentation/gitrelease-notes.txt | 37 +++++++++++++++++++++++++++++++++++++
2 files changed, 38 insertions(+)
create mode 100644 Documentation/gitrelease-notes.txt
--
1.8.3.msysgit.0
next reply other threads:[~2014-02-15 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 10:29 Philip Oakley [this message]
2014-02-15 10:29 ` [PATCH] [PATCH] Provide a release-notes man page / guide Philip Oakley
2014-02-18 22:14 ` [PATCH] Git release notes man page Junio C Hamano
2014-02-18 22:54 ` Philip Oakley
2014-02-19 9:06 ` Stefan Näwe
2014-02-19 18:22 ` Junio C Hamano
2014-02-18 23:05 ` 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=1392460179-776-1-git-send-email-philipoakley@iee.org \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=stefan.naewe@atlas-elektronik.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).