7:07 p.m.
Whenever we change any of the embedded API docs or add new APIs we end up
with huge diffs on the docs/APIchunk*.html files. These HTML files don't
seem to be visible anywhere on the website, nor are there even any <a href>
links to them in other pages on the website.
Can we just kill off these APIchunk* files from the doc generator in CVS
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
4:42 a.m.
On Tue, Jan 15, 2008 at 01:07:17AM +0000, Daniel P. Berrange wrote:
Whenever we change any of the embedded API docs or add new APIs we
end up
with huge diffs on the docs/APIchunk*.html files. These HTML files don't
seem to be visible anywhere on the website, nor are there even any <a href>
links to them in other pages on the website.
Can we just kill off these APIchunk* files from the doc generator in CVS
Bahh, yes ... inheritance from libxml2, where they make more sense since
the API is huge. In libvirt it's not useful, really. Know how to do it
or do you want me to clean this up ?
Daniel
--
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard | virtualization library http://libvirt.org/
veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
12:03 p.m.
On Sat, Jan 19, 2008 at 05:42:46AM -0500, Daniel Veillard wrote:
On Tue, Jan 15, 2008 at 01:07:17AM +0000, Daniel P. Berrange wrote:
> Whenever we change any of the embedded API docs or add new APIs we end up
> with huge diffs on the docs/APIchunk*.html files. These HTML files don't
> seem to be visible anywhere on the website, nor are there even any <a href>
> links to them in other pages on the website.
>
> Can we just kill off these APIchunk* files from the doc generator in CVS
Bahh, yes ... inheritance from libxml2, where they make more sense since
the API is huge. In libvirt it's not useful, really. Know how to do it
or do you want me to clean this up ?
I've not looked at exactly how they are generated - so if you know how
to remove them go ahead..
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
2:09 a.m.
On Sat, Jan 19, 2008 at 06:03:46PM +0000, Daniel P. Berrange wrote:
On Sat, Jan 19, 2008 at 05:42:46AM -0500, Daniel Veillard wrote:
> On Tue, Jan 15, 2008 at 01:07:17AM +0000, Daniel P. Berrange wrote:
> > Whenever we change any of the embedded API docs or add new APIs we end up
> > with huge diffs on the docs/APIchunk*.html files. These HTML files don't
> > seem to be visible anywhere on the website, nor are there even any <a
href>
> > links to them in other pages on the website.
> >
> > Can we just kill off these APIchunk* files from the doc generator in CVS
>
> Bahh, yes ... inheritance from libxml2, where they make more sense since
> the API is huge. In libvirt it's not useful, really. Know how to do it
> or do you want me to clean this up ?
I've not looked at exactly how they are generated - so if you know how
to remove them go ahead..
Yup, done in CVS,
Daniel
--
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard | virtualization library http://libvirt.org/
veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
6152
days inactive
6158
days old
3 comments
2 participants
participants (2)
-
Daniel P. Berrange -
Daniel Veillard