From: "Philip Oakley" <philipoakley@iee.org>
To: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>
Cc: "GitList" <git@vger.kernel.org>
Subject: Re: [PATCH 0/6] Make 'git help everyday' work -> relnotes
Date: Tue, 21 Jan 2014 22:25:26 -0000 [thread overview]
Message-ID: <BA4E87FA92ED4E8FB2C00F013BD7B3FF@PhilipOakley> (raw)
In-Reply-To: 52D91B0E.6080000@atlas-elektronik.com
From: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>
> Am 16.01.2014 22:14, schrieb Philip Oakley:
>> From: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>
>> [...]
>>>
>>> I'd really like to see 'git help relnotes' working as well...
>>>
>>> Stefan
>>
>> Stefan,
>>
>> Were you thinking that all the release notes would be quoted verbatim
>> in
>> the one long man page?
>>
>> Or that it would be a set of links to each of the individual text
>> files
>> (see the ifdef::stalenotes[] in git/Documentation/git.txt)?
>>
>> The latter allows individual release notes to be checked, but still
>> leaves folks with a difficult search problem if they want to find
>> when
>> some command was 'tweaked'.
>>
>> Obviously, any method would need to be easy to maintain. And the
>> RelNotes symlink would need handling.
>
> 'git help relnotes' should show the current release note with
> a link to the previous.
OK, that seems very sensible, as the concatenated release notes run to
15k lines!
Determining which is the current release note is possibly more
problematic, which should be when making the documentation.
>
> And 'git help git' should link to the current release note.
>
In some sense that 'current' should be the same as the 'git --version',
but through an assumption of a common distribution of git and the
documentation, rather than any run time determination.
At the moment the Documenation/git.txt 'stalenotes' section could be
separated into its own file to act as the basis for the links, but as
yet I don't have a good view as to how the current release notes (with /
without maint notes?) would be embedded without a maintenance burden for
Junio.
Philip
next prev parent reply other threads:[~2014-01-21 22:25 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 [this message]
2014-01-21 23:28 ` Junio C Hamano
2014-01-22 0:22 ` Philip Oakley
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=BA4E87FA92ED4E8FB2C00F013BD7B3FF@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--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