From: Mark Wielaard <mark@klomp.org>
To: frysk@sourceware.org
Cc: Andrew Cagney <cagney@redhat.com>
Subject: Re: Fixed javadoc generation and created html manpages
Date: Mon, 17 Mar 2008 11:00:00 -0000 [thread overview]
Message-ID: <1205751221.7607.41.camel@localhost.localdomain> (raw)
In-Reply-To: <1205424214.26429.10.camel@dijkstra.wildebeest.org>
Hi Andrew,
On Thu, 2008-03-13 at 17:03 +0100, Mark Wielaard wrote:
> This patch fixes the generation of javadoc by using the javadoc that
> comes with icedtea/openjdk. It misses some of the nice features of
> gjdoc, but it looks like it will at least be included in most distros in
> the near future.
>
> It also adds generation of html versions of the manpages so we have a
> list of those on the site: http://sourceware.org/frysk/manpages/
> I made a reference to them from the documentation page.
>
> The files in htdocs get updated automagically whenever you do a git
> push, for reuploading the javadoc and manpages dirs you need rsync
> access to sourceware. I can setup an autobuilder/pusher for this if
> nobody else has already.
>
> Andrew, I assume you have one since the javadoc directory is currently
> owned by you, but not group frysk, so I wasn't able to update those yet.
> Could you chown -R g+w and chgrp -R frysk them, or start your own
> builder and do a make javadoc upload-javadoc?
I saw you fixed the permission problems and improved the output a bit
with:
commit 963501ea208d03400e55c48ff8e28053f6b8e5b7
Author: Andrew Cagney <cagney@redhat.com>
Date: Fri Mar 14 16:07:14 2008 -0400
Separate out/fix DEFAULT test.
frysk-sys/frysk/rsl/ChangeLog
2008-03-14 Andrew Cagney <cagney@redhat.com>
* TestLog.java (testDefault()): New.
commit bd3b09d90dfd03c064314fb8a86e9a64a77ce0eb
Author: Andrew Cagney <cagney@redhat.com>
Date: Fri Mar 14 15:49:54 2008 -0400
Fix html man-page nits.
frysk-common/ChangeLog
2008-03-14 Andrew Cagney <cagney@redhat.com>
* manpages.sh: New.
* frysk.xml: New.
frysk-core/frysk/bindir/ChangeLog
2008-03-14 Andrew Cagney <cagney@redhat.com>
* frysk.xml: New.
* fparser.xml, fparser.java: Move to frysk.pkglibdir.
* fauxv.xml: Cite frysk(7), simplify url.
* fcatch.xml: Ditto.
* fcore.xml: Ditto.
* fdebuginfo.xml: Ditto.
* fdebugrpm.xml: Ditto.
* ferror.xml: Ditto.
* fexe.xml: Ditto.
* fhpd.xml: Ditto.
* fmaps.xml: Ditto.
* fparser.xml: Ditto.
* fstack.xml: Ditto.
* fstep.xml: Ditto.
* ftrace.xml: Ditto.
frysk-core/frysk/pkglibdir/ChangeLog
2008-03-14 Andrew Cagney <cagney@redhat.com>
* fparser.xml, fparser.java: Move to here from frysk.bindir.
* funit-threads.xml: Cite frysk(7); update url.
* funit-slave.xml: Ditto.
* funit-exit.xml: Ditto.
* funit-exec.xml: Ditto.
frysk-gui/frysk/bindir/ChangeLog
2008-03-14 Andrew Cagney <cagney@redhat.com>
* frysk.xml: Cite frysk(7).
frysk-sys/frysk/pkglibdir/ChangeLog
2008-03-14 Andrew Cagney <cagney@redhat.com>
* fsystest.xml: Cite frysk(7), update url.
* funit-procmask.xml: Ditto.
frysk-top/ChangeLog
2008-03-14 Andrew Cagney <cagney@redhat.com>
* Makefile.am (frysk-common/frysk.7): New target.
(manpages): Move code to frysk-common/manpages.sh.
Very nice cleanup.
Do we have something that auto-generates and pushes changes to javadoc
and manpages onto sourceware or should I set up something for that?
Thanks,
Mark
prev parent reply other threads:[~2008-03-17 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 16:04 Mark Wielaard
2008-03-13 17:49 ` Mark Wielaard
2008-03-17 11:00 ` Mark Wielaard [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=1205751221.7607.41.camel@localhost.localdomain \
--to=mark@klomp.org \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).