Adam Thompson <[email protected]> writes: > Do we have some form of issue tracker which works with edbrowse (I'm not sure > how edbrowse-friendly the github setup is)?
Well, the github issue tracker isn't edbrowse-friendly at all. Github uses lots and lots of ajax and other fancy web stuff. However, they do provide an API for programmatic access. A few years back, I wrote a command-line interface to github, using their API. It works well with their issue tracker. You can clone the code here: git://github.com/CMB/cligh.git Coincidentally, this is the program I used to give you and Karl push access to the main repository. It's written in Python. Also, it requires a couple of external dependencies, one of which is probably not packaged on most distributions. I suspect this is a problem for some people. > On the subject of 3.4.11, apart from the js lib change and other bug fixes, > are there any other features or major changes we want to make before it > happens I don't think so. -- Chris _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
