From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2011, #06; Wed, 21)
Date: Fri, 23 Sep 2011 01:33:32 +0200 [thread overview]
Message-ID: <201109230133.33214.jnareb@gmail.com> (raw)
In-Reply-To: <7v4o04xjcb.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> --------------------------------------------------
>>> [New Topics]
>>
>>> * jc/namespace-doc-with-old-asciidoc (2011-09-16) 1 commit
>>> - Documentation/gitnamespaces.txt: cater to older asciidoc
>>
>> I'll need this to e.g. test the "rpm" target after adding
>> Documentation/gitweb.txt and Documentation/gitweb.conf.txt
>>
>> But it is not something very urgent...
>
> Now I am confused. If you apply your patch on top of "master" then you
> cannot create "rpm" on your platform, not because your patch is busted,
> but because "master" lacks the documentation fix from that topic. Is that
> what you mean?
Yes, that is what I mean... but that it is only because I use old
version of asciidoc (7.1.2).
"make doc" (which is part of "make rpm") fails on my box with
ASCIIDOC gitnamespaces.html
ERROR: gitnamespaces.txt: line 9: second section must be named SYNOPSIS
make[1]: *** [gitnamespaces.html] Error 1
> If the reason the documentation fix for "master" is needed is because a
> new feature scheduled for the upcoming release has broken documentation,
> then wouldn't we need the fix before the release, whether you are working
> on your patch or not? How can it be not urgent if that is the case?
>
> On my boxes with recent Debian, Ubuntu, and F14, I am not suffering from
> the lack of the workaround, but if distros need the workaround, then the
> time to apply it is now, not post release.
I don't think _modern_ distributions need this workaround... asciidoc 8.4.5
which fixed the issue with "Synopsis" section was released 2009-05-24:
http://www.methods.co.nz/asciidoc/CHANGELOG.html
Version 8.4.5 (2009-05-24)
--------------------------
Additions and changes
~~~~~~~~~~~~~~~~~~~~~
* Added manpage "Name" and "Synopsis" section title customization to
languages configuration files.
* "Synopsis" manpage section no longer mandatory.
[...]
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2011-09-22 23:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 5:04 What's cooking in git.git (Sep 2011, #06; Wed, 21) Junio C Hamano
2011-09-22 8:37 ` Carlos Martín Nieto
2011-09-22 9:14 ` Michael Schubert
2011-09-22 16:39 ` Junio C Hamano
2011-09-22 23:01 ` Jakub Narebski
2011-09-22 23:12 ` Junio C Hamano
2011-09-22 23:33 ` Jakub Narebski [this message]
2011-09-22 23:45 ` Junio C Hamano
2011-09-23 11:00 ` [PATCH] fix push --quiet: add 'quiet' capability to receive-pack Clemens Buchacher
2011-09-23 11:55 ` [PATCH] use -h for synopsis and --help for manpage consistently Clemens Buchacher
2011-09-23 14:44 ` What's cooking in git.git (Sep 2011, #06; Wed, 21) Scott Chacon
2011-09-23 18:00 ` Junio C Hamano
2011-09-23 19:29 ` Junio C Hamano
2011-09-26 14:03 ` Scott Chacon
2011-09-26 18:52 ` Junio C Hamano
2011-09-27 2:08 ` Jay Soffian
[not found] ` <20111003182136.GA6136@ecki.lan>
2011-10-03 22:03 ` [PATCH] use -h for synopsis and --help for manpage consistently Junio C Hamano
2011-10-05 6:33 ` Clemens Buchacher
2011-10-05 6:31 ` [PATCH] fix push --quiet: add 'quiet' capability to receive-pack Clemens Buchacher
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=201109230133.33214.jnareb@gmail.com \
--to=jnareb@gmail.com \
--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 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.