From: Thomas Rast <trast@student.ethz.ch>
To: <git@vger.kernel.org>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Jakub Narebski" <jnareb@gmail.com>,
"Sverre Rabbelier" <srabbelier@gmail.com>
Subject: [RFC PATCH v2 0/3] Documentation: refactor config variable descriptions
Date: Fri, 22 Oct 2010 07:02:28 +0200 [thread overview]
Message-ID: <cover.1287690696.git.trast@student.ethz.ch> (raw)
This resurrects (finally) the earlier attempt at
http://mid.gmane.org/cover.1280169048.git.trast@student.ethz.ch
It tries the inverse approach: teaching the script how to find config
variable blocks in each manpage, and then linking them from the main
list. (Obviously just inserting them into the main list could also
work.)
In other words, it attempts to push out the "original" documentation
of each variable from the main list to the individual manpage, which
is exactly opposite from v1.
This has the advantage that it does not make the source .txt for each
manpage "unreadable by themselves", as the earlier approach did (and
Jonathan noticed).
It also has the advantage that it will shrink config-vars.txt over
time.
Instead of going through all manpages again, I just tacked on a sample
patch as 3/3 that shows what the use/effect could be. Once we settle
on the direction (v1 or v2) of the refactoring, I'll make more patches
or resurrect the old ones.
I'm afraid 1/3 (semantically unchanged from the equivalent patch in
v1) will again not make it through, so I again pushed this out:
git://repo.or.cz/git/trast.git t/doc-config-extraction-v2
(incidentally v1 is still there as t/doc-config-extraction). I based
it on master; 1/3 is prone to conflicts but can easily be recreated
from scratch.
Thomas Rast (3):
Documentation: Move variables from config.txt to separate file
Documentation: complete config list from other manpages
Documentation: move format.* documentation to format-patch
Documentation/Makefile | 9 +-
Documentation/config-vars-src.txt | 1691 +++++++++++++++++++++++++++++++++
Documentation/config.txt | 1748 +----------------------------------
Documentation/git-format-patch.txt | 65 ++-
Documentation/make-config-list.perl | 131 +++
5 files changed, 1892 insertions(+), 1752 deletions(-)
create mode 100644 Documentation/config-vars-src.txt
create mode 100755 Documentation/make-config-list.perl
--
1.7.3.1.281.g5da0b
next reply other threads:[~2010-10-22 5:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 5:02 Thomas Rast [this message]
2010-10-22 5:02 ` [RFC PATCH v2 3/3] Documentation: move format.* documentation to format-patch Thomas Rast
[not found] ` <c3f621cd062b2c4f80aa2e8dadcfddbc042aefaa.1287690696.git.trast@student.ethz.ch>
2010-10-22 8:18 ` [RFC PATCH v2 1/3] Documentation: Move variables from config.txt to separate file Jakub Narebski
[not found] ` <8145782bddf60325909f328337cb76d25c4402cf.1287690696.git.trast@student.ethz.ch>
2010-10-22 6:19 ` [RFC PATCH v2 2/3] Documentation: complete config list from other manpages Jakub Narebski
2010-10-22 14:31 ` Jakub Narebski
2010-10-23 22:24 ` [PATCH] " Thomas Rast
2010-10-23 22:30 ` Jakub Narebski
2010-10-24 14:36 ` Jakub Narebski
2010-10-24 20:44 ` [RFC PATCH v3 2/3] " Jakub Narebski
2010-10-24 20:55 ` [RFC PATCH v3 2/3 (amend)] " Jakub Narebski
2010-10-22 15:17 ` [RFC PATCH v2 0/3] Documentation: refactor config variable descriptions Jakub Narebski
2010-10-22 15:53 ` Jeff King
2010-10-24 1:24 ` Thomas Rast
2010-10-25 15:04 ` Jeff King
2010-10-25 12:44 ` Jakub Narebski
2010-10-25 15:11 ` Jeff King
2010-10-25 15:49 ` Jakub Narebski
2010-10-27 10:56 ` Jakub Narebski
2010-11-02 13:42 ` Jens Lehmann
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=cover.1287690696.git.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=jrnieder@gmail.com \
--cc=srabbelier@gmail.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).