My intention is to link it to the website, so we have browsable documentation
> Date: Mon, 7 Nov 2011 19:26:23 -0800
> From: currens.ch...@gmail.com
> To: lucene-net-dev@lucene.apache.org
> Subject: Re: [Lucene.Net] Lucene.Net-2.9.4-i
I don't understand why we have the rendered html in the docs. I don't mind
having the .chm rendered and put in the repo, but the entire HTML
documentation spans 8,000 files and over 100mb. The CHM comes in at around
15mb.
I don't think it's necessary to have both in the repo, but if the consensu
On 2011-11-07, Michael Herndon wrote:
> I can rebuild it, but the trick is replacing the version of it in svn so
> that it does not cause svnsync and cms to choke. Last time I just pushed it
> into branch/site/docs. However, that is not publicly visible for the
> incubation website, so Prescott h
I can rebuild it, but the trick is replacing the version of it in svn so
that it does not cause svnsync and cms to choke. Last time I just pushed it
into branch/site/docs. However, that is not publicly visible for the
incubation website, so Prescott had to do an svn move.
I'm not quite sure how t
I've committed the changes to the xml documentation to the repo.
I built the documentation, but I wasn't sure how Michael packaged the
documentation in [LUCENENET-452]. If someone could either rebuild the
documentation or let me know how it was done for the release, then we can
open it up for ano
I dont mind
Sent from my Windows Phone
From: Christopher Currens
Sent: 11/4/2011 5:08 PM
To: lucene-net-dev@lucene.apache.org
Subject: [Lucene.Net] Lucene.Net-2.9.4-incubator-RC2 Documentation
A few days ago, after RC1 was put up for a vote to release, I started
w
