From: Petr Baudis <pasky@suse.cz>
To: Paul Dickson <paul@permanentmail.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Cogito-0.16.1
Date: Tue, 13 Dec 2005 23:31:14 +0100 [thread overview]
Message-ID: <20051213223114.GF22159@pasky.or.cz> (raw)
In-Reply-To: <20051213110257.a37be18b.paul@permanentmail.com>
Dear diary, on Tue, Dec 13, 2005 at 07:02:57PM CET, I got a letter
where Paul Dickson <paul@permanentmail.com> said that...
> On Tue, 13 Dec 2005 17:56:45 +0100, Petr Baudis wrote:
>
> > Dear diary, on Tue, Dec 13, 2005 at 02:26:36AM CET, I got a letter
> > where Paul Dickson <paul@permanentmail.com> said that...
> > > Any chance of man files? I'm more use to type man than cg-help.
> >
> > You can make the man files by
> >
> > make doc
> >
> > and install them by
> >
> > make install-doc
> >
> >
> > This isn't done by default so that you won't need asciidoc for the
> > build. This is exactly the same way in GIT.
>
> See my messages about 0.99.9m and xmlto (and asciidoc). They are
> currently required for building the RPMs. Perhaps the spec file needs
> updating.
But the spec file also makes the 'doc' and 'install-doc' targets. When
you act as a packager, asciidoc becomes a reasonable build-time
requirement.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-12-13 22:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 1:12 [ANNOUNCE] Cogito-0.16.1 Petr Baudis
2005-12-12 1:14 ` Petr Baudis
2005-12-12 3:03 ` Don Koch
2005-12-13 1:02 ` Problems with cg-admin-setuprepo Paul Dickson
2005-12-13 1:16 ` Petr Baudis
2005-12-13 1:26 ` [ANNOUNCE] Cogito-0.16.1 Paul Dickson
2005-12-13 16:56 ` Petr Baudis
2005-12-13 18:02 ` Paul Dickson
2005-12-13 22:31 ` Petr Baudis [this message]
2005-12-14 1:40 ` Paul Dickson
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=20051213223114.GF22159@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=paul@permanentmail.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).