From: "Philip Oakley" <philipoakley@iee.org>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>,
GitList <git@vger.kernel.org>
Subject: Re: [PATCH 0/6] Make 'git help everyday' work -> relnotes
Date: Wed, 22 Jan 2014 00:22:19 -0000 [thread overview]
Message-ID: <2D10AF8E0C024CC5A817528582FDE07D@PhilipOakley> (raw)
In-Reply-To: xmqqob34synq.fsf@gitster.dls.corp.google.com
From: "Junio C Hamano" <gitster@pobox.com>
> "Philip Oakley" <philipoakley@iee.org> writes:
>
>> Determining which is the current release note is possibly more
>> problematic, which should be when making the documentation.
>
> Hmmm.... Why?
>
> You are already aware of the stale-notes section, no? Isn't the top
> one the latest?
It's that the 'git help release-notes' would _include_ the latest
release notes, not just link to them (which is what the stalenotes
currently does). Or at least that was the idea.
Trying to determine the latest version, and then include those release
notes, and the subsequent maint notes, into the putative
"release-notes(7)" man page, without causing you any maintenance hassle,
was the conceptual problem.
I already have a local patch that creates a stalenote.txt file, and
includes that in a "release-notes(7)" man page, but it still leaves the
actual release notes in a separate plain text file, linked from the man
page, rather than being right at hand, which is what I think readers
would expect.
My other question would be to ask how you normally manage the up-issue
of the stalenotes, and when you would normally create that section in
git(1) as I didn't see any ifdef::stalenotes[] being defined anywhere
else.
Philip
next prev parent reply other threads:[~2014-01-22 0:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 23:13 [PATCH 0/6] Make 'git help everyday' work Philip Oakley
2014-01-09 23:13 ` [PATCH 1/6] copy everyday.txt to giteveryday.txt Philip Oakley
2014-01-09 23:13 ` [PATCH 2/6] Update giteveryday.txt to fit man page formatting Philip Oakley
2014-01-09 23:13 ` [PATCH 3/6] add giteveryday to the manpages make list Philip Oakley
2014-01-09 23:13 ` [PATCH 4/6] Add deprecation note to old everyday.txt Philip Oakley
2014-01-09 23:13 ` [PATCH 5/6] add 'everyday' to the help --guides list Philip Oakley
2014-01-09 23:13 ` [PATCH 6/6] Update git(1) link to giteveryday Philip Oakley
2014-01-09 23:49 ` [PATCH 0/6] Make 'git help everyday' work Junio C Hamano
2014-01-10 8:06 ` Philip Oakley
2014-01-10 18:09 ` Junio C Hamano
2014-01-10 18:59 ` Philip Oakley
2014-01-11 19:50 ` Philip Oakley
2014-01-10 8:18 ` Stefan Näwe
2014-01-16 21:14 ` [PATCH 0/6] Make 'git help everyday' work -> relnotes Philip Oakley
2014-01-17 11:59 ` Stefan Näwe
2014-01-21 22:25 ` Philip Oakley
2014-01-21 23:28 ` Junio C Hamano
2014-01-22 0:22 ` Philip Oakley [this message]
2014-01-22 0:40 ` Junio C Hamano
2014-01-22 8:33 ` Philip Oakley
2014-01-10 20:19 ` [PATCH 0/6] Make 'git help everyday' work Jonathan Nieder
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=2D10AF8E0C024CC5A817528582FDE07D@PhilipOakley \
--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