Github has an interesting approach to how it generates the optional "Github
pages" documentation. It uses a specific branch ("gh-pages") from your
repository, to generate them.
Assuming I'm understanding this properly, one potential option would be to have
a specific branch that the documentation up on the web server is generated from.
--Vlad
On Oct 3, 2012, at 7:06 PM, Robin Sommer <[email protected]> wrote:
>
> On Wed, Oct 03, 2012 at 17:06 -0500, you wrote:
>
>> If you want, you could just merge it into master, then I can
>> change it later to point to the "Installing Bro" material
>> (as part of my documentation work for 2.2).
>
> Sounds good.
>
> Btw, it's a bit unfortunate that we have put the FAQ document into the
> distribution as that means it won't update on the web server until the
> next release comes out. That's something I think we should chnage in
> the future: the FAQ shouldn't be tied to a specific version but
> maintained separately as a web page instead.
>
> Robin
>
> --
> Robin Sommer * Phone +1 (510) 722-6541 * [email protected]
> ICSI/LBNL * Fax +1 (510) 666-2956 * www.icir.org
> _______________________________________________
> bro-dev mailing list
> [email protected]
> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
