I've also a bug list here, that I'll try to fix when I have some time.
I don't think that branching is the right way to go. I prefer posting my
patches somewhere with a description and then let someone to review, comment
and apply/discard them.
I agree. My branch proposal was because it seemed the
Instead of non-specific head is broken email, why not point out what
is broken?
Livedocs is running fine here; I built it only a week or so ago with
no problems.
Plus, I have a mirror that updates daily (livedocs.thebrainroom.net)
with no problems (assuming that someone hasn't broken phpdoc)
Hi Sean,
Currently the way of getting changes commited to the 'livedocs' in CVS
is to submit patches to those who have karma. When submitting
patches, remeber to do 'cvs diff -u' and save this patch to your
website and mail them the link and explain to them what you are trying
to do with the
What is the current status of livedocs development?
Accepting patches (applied mostly by Ilia and Wez).
There are several outstanding issues with the livedocs code. As I said
in my post, last night, HEAD seems broken. Also, Nuno has a number of
patches available at http://livedocs.aborla.net/
It
On August 14, 2004 04:23 pm, you wrote:
There are several outstanding issues with the livedocs code. As I said
in my post, last night, HEAD seems broken. Also, Nuno has a number of
patches available at http://livedocs.aborla.net/
It would be nice if Ilia (and/or Wez) could review these
Ilia,
I reviewed the patches and applied 7 of them, thanks guys.
The Cygwin patch was not applied because I have not way to test it and the
last person I spoke to who build the manual on win32 via Cygwin had no
issues.
What in HEAD is broken?
Thank you very much. I know you're busy, I really
