git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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] [PATCH] Provide a release-notes man page / guide
Date: Sat, 15 Feb 2014 10:29:39 +0000	[thread overview]
Message-ID: <1392460179-776-2-git-send-email-philipoakley@iee.org> (raw)
In-Reply-To: <1392460179-776-1-git-send-email-philipoakley@iee.org>

Use the symlinked RelNote file as a list-block to
act as the core of the release-notes man page.

The mantainers work load should not be affected.

Signed-off-by: Philip Oakley <philipoakley@iee.org>
---

The included lines are inset 11 spaces by the man page
asciidoc formatting so some are more than 80 characters long.
No negative indent mechanism for the list block was found -
suggestions welcomed.

The use of the stalenotes section from git(1) was rejected.

The stalenotes, with over two hundred links, has greater than
2 digits allowed in the trailing link list on the man page,
so would miss the hundreds digit.

Also the html links for the "documentation for release x.y.z"
(at kerenel.org) are to html files that are not actually made
by the makefile.
---
 Documentation/Makefile             |  1 +
 Documentation/gitrelease-notes.txt | 37 +++++++++++++++++++++++++++++++++++++
 2 files changed, 38 insertions(+)
 create mode 100644 Documentation/gitrelease-notes.txt

diff --git a/Documentation/Makefile b/Documentation/Makefile
index fc6b2cf..b599b1f 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -29,6 +29,7 @@ MAN7_TXT += gitdiffcore.txt
 MAN7_TXT += gitglossary.txt
 MAN7_TXT += gitnamespaces.txt
 MAN7_TXT += gitrevisions.txt
+MAN7_TXT += gitrelease-notes.txt
 MAN7_TXT += gittutorial-2.txt
 MAN7_TXT += gittutorial.txt
 MAN7_TXT += gitworkflows.txt
diff --git a/Documentation/gitrelease-notes.txt b/Documentation/gitrelease-notes.txt
new file mode 100644
index 0000000..29d9b1b
--- /dev/null
+++ b/Documentation/gitrelease-notes.txt
@@ -0,0 +1,37 @@
+gitrelease-notes(7)
+===================
+
+NAME
+----
+gitrelease-notes - the onward progress of the stupid content tracker
+
+
+SYNOPSIS
+--------
+[verse]
+'git help release-notes'
+
+DESCRIPTION
+-----------
+
+Provide the release notes for the latest (possibly
+unreleased) version of Git, that is available from 'master'
+branch of the `git.git` repository.
+
+RELEASE NOTES
+-------------
+
+----
+include::../RelNotes[]
+----
+
+OLDER RELEASE NOTES
+-------------------
+
+Release notes for older versions are available in the Git source
+Documentation/RelNotes/ folder. This is currently available at
+https://code.google.com/p/git-core/source/browse/
+
+GIT
+---
+Part of the linkgit:git[1] suite
-- 
1.8.3.msysgit.0

  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 [PATCH] Git release notes man page Philip Oakley
2014-02-15 10:29 ` Philip Oakley [this message]
2014-02-18 22:14 ` 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-2-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).