From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: [PATCH v2 0/2] DEFAULT_DOC_TARGET
Date: Thu, 3 Jan 2013 11:05:18 -0800 [thread overview]
Message-ID: <1357239920-2201-1-git-send-email-gitster@pobox.com> (raw)
This allows things like:
$ DEFAULT_DOC_TARGET=html make doc
$ DEFAULT_DOC_INSTALL_TARGET=html make install-doc
on a platform that does not have manpage viewer. Which is not very
useful, given that you can already say
$ make install-html
on such a platform, and these install-$format targets will not go
away.
The real motivation behind this was to let me say:
$ git checkout $some_old_fork_point
$ DEFAULT_DOC_TARGET=git-push.1 make doc
while updating the sources to the documentation for the maintainance
track, without having to format everything else that is different
between the old fork point and the primary branch I usually work on.
The first one was discussed some time ago on the list and all the
fixes mentioned on the thread already squashed in. The second one
is merely for completeness.
For previous round, see:
http://thread.gmane.org/gmane.comp.version-control.git/207193/focus=207201
Junio C Hamano (2):
Allow generating a non-default set of documentation
Allow installing a non-default set of documentation
Documentation/Makefile | 10 ++++++++--
Makefile | 13 ++++++++++++-
2 files changed, 20 insertions(+), 3 deletions(-)
--
1.8.1.293.g4a210a9
next reply other threads:[~2013-01-03 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 19:05 Junio C Hamano [this message]
2013-01-03 19:05 ` [PATCH v2 1/2] Allow generating a non-default set of documentation Junio C Hamano
2013-01-03 19:05 ` [PATCH v2 2/2] Allow installing " Junio C Hamano
2013-01-03 20:32 ` [PATCH v2 0/2] DEFAULT_DOC_TARGET Jeff King
2013-01-03 20:37 ` Jeff King
2013-01-03 21:05 ` Jeff King
2013-01-03 21:07 ` Jeff King
2013-01-03 22:20 ` Junio C Hamano
2013-01-03 22:25 ` Jeff King
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=1357239920-2201-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).