From: Philip Oakley <philipoakley@iee.org>
To: GitList <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v3 0/3] Make 'git help everyday' work
Date: Mon, 29 Sep 2014 17:41:44 +0100 [thread overview]
Message-ID: <1412008907-3988-1-git-send-email-philipoakley@iee.org> (raw)
Here's version three of my patches to make 'git help everyday' work.
It's taken awhile. Previous patches at [1] and [2].
Junio has provided guidance on modernisation of the text, which has
been integrated into patch 1.
Patch 2 regularises the OBSOLETE_HTML method in the make file, in line
with the currently queued version on pu.
Finally patch 3 swaps over the everyday.txt to the giteveryday.txt accessible
through the regular help system, and changes over all the links.
This follows from :
>Subject: What's cooking in git.git (Sep 2014, #06; Wed, 24)
[...]
> * po/everyday-doc (2014-01-27) 1 commit
> - Make 'git help everyday' work
>
> This may make the said command to emit something, but the source is
> not meant to be formatted into a manual pages to begin with, and
> also its contents are a bit stale. It may be a good first step in
> the right direction, but needs more work to at least get the
> mark-up right before public consumption.
>
> Waiting for a reroll (thread ending at $gmane/254746)
>
Philip
[1] http://thread.gmane.org/gmane.comp.version-control.git/240286
[PATCH 0/6] Make 'git help everyday' work
[2] http://thread.gmane.org/gmane.comp.version-control.git/240354
[PATCH v2] Make 'git help everyday' work
Philip Oakley (3):
doc: modernise everyday.txt wording and format in man page style
doc: Makefile regularise OBSOLETE_HTML list building
Make 'git help everyday' work
Documentation/Makefile | 6 +-
Documentation/everyday.txt | 413 ----------------------------------
Documentation/everyday.txto | 9 +
Documentation/git-push.txt | 2 +-
Documentation/git.txt | 4 +-
Documentation/gitcore-tutorial.txt | 2 +-
Documentation/gitcvs-migration.txt | 2 +-
Documentation/giteveryday.txt | 447 +++++++++++++++++++++++++++++++++++++
Documentation/gitglossary.txt | 2 +-
Documentation/gittutorial-2.txt | 4 +-
Documentation/gittutorial.txt | 4 +-
README | 2 +-
builtin/help.c | 1 +
13 files changed, 472 insertions(+), 426 deletions(-)
delete mode 100644 Documentation/everyday.txt
create mode 100644 Documentation/everyday.txto
create mode 100644 Documentation/giteveryday.txt
--
1.9.4.msysgit.0
next reply other threads:[~2014-09-29 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 16:41 Philip Oakley [this message]
2014-09-29 16:41 ` [PATCH v3 1/3] doc: modernise everyday.txt wording and format in man page style Philip Oakley
2014-09-29 23:24 ` Junio C Hamano
2014-09-29 16:41 ` [PATCH v3 2/3] doc: Makefile regularise OBSOLETE_HTML list building Philip Oakley
2014-09-29 16:41 ` [PATCH v3 3/3] Make 'git help everyday' work Philip Oakley
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=1412008907-3988-1-git-send-email-philipoakley@iee.org \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).