From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Chris Johnsen <chris_johnsen@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-push.txt: describe how to default to pushing only current branch
Date: Sun, 15 Mar 2009 21:51:24 -0700 [thread overview]
Message-ID: <7v4oxu135f.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090314214603.GA20418@sigill.intra.peff.net> (Jeff King's message of "Sat, 14 Mar 2009 17:46:03 -0400")
Jeff King <peff@peff.net> writes:
> On Sat, Mar 14, 2009 at 02:25:11PM -0700, Junio C Hamano wrote:
>
>> Jeff King <peff@peff.net> writes:
>>
>> > Actually, looking closer, the information seems to be lost entirely.
>> > Asciidoc renders this to <literal> in the XML, but docbook seems to
>> > throw it away when converting to a manpage. In theory it's possible to
>> > apply our own xsl style to turn this into something else, and I think
>> > that is a better solution than just trying to fix this one spot.
>>
>> When I check the asciidoc output for manpages (which I rarely do), I often
>> render it to Postscript to see the typesetting. I guess not many people
>> consider manpages are for printing anymore but are solely for monospaced
>> terminal consumption these days.
>
> How do you render it? From the XML, or from the roff? Because if I am
> reading it right (which it is entirely possible that I am not), the
> information is lost in the roff version. And that is the version I would
> expect people to be looking at (via man -Tps, or just plain man).
I was agreeing with you; I let "man -Tps -l git-foo.1" render from roff
input and I can see that the output from asciidoc toolchain) prepared as
roff input does not consider printed pages so important anymore.
prev parent reply other threads:[~2009-03-16 4:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 7:48 Not pushing all branches? Peter Krefting
2009-03-13 8:12 ` Imran M Yousuf
2009-03-13 9:44 ` Peter Krefting
2009-03-13 10:49 ` Johannes Schindelin
2009-03-13 11:38 ` Finn Arne Gangstad
2009-03-13 8:25 ` John Tapsell
2009-03-13 10:51 ` Johannes Schindelin
2009-03-13 12:37 ` John Tapsell
2009-03-13 13:53 ` Johannes Schindelin
2009-03-13 13:56 ` John Tapsell
2009-03-13 15:48 ` Michael J Gruber
2009-03-13 16:00 ` Johannes Schindelin
2009-03-13 20:02 ` Junio C Hamano
2009-03-14 1:08 ` Miles Bader
2009-03-17 8:24 ` Jeff King
2009-03-13 16:49 ` Jeff King
2009-03-14 1:27 ` [PATCH] git-push.txt: describe how to default to pushing only current branch Chris Johnsen
2009-03-14 19:26 ` Junio C Hamano
2009-03-15 2:32 ` [PATCH v2] " Chris Johnsen
2009-03-14 20:34 ` [PATCH] " Jeff King
2009-03-14 20:56 ` Jeff King
2009-03-15 2:49 ` Chris Johnsen
2009-03-15 11:30 ` [PATCH] git-push.txt: describe how to default to pushing only Chris Johnsen
2009-03-17 7:46 ` [PATCH] git-push.txt: describe how to default to pushing only current branch Jeff King
2009-03-14 21:25 ` Junio C Hamano
2009-03-14 21:46 ` Jeff King
2009-03-16 4:51 ` Junio C Hamano [this message]
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=7v4oxu135f.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chris_johnsen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.