Le 12 oct. 05 à 21:53, Gunnar Farnebäck a écrit :
There are two more resources which give superior functionality with
less work than the corresponding parts of patches.html.
1. http://trac.gnugo.org/gnugo/report/9 (linked as "Pending patches"
from the front page http://trac.gnugo.org). This lists all pending
patches entered as tickets.
2. http://trac.gnugo.org/gnugo/log/?verbose=on (linked as "Recent CVS
commits" from the front page). This shows all recent CVS mainline
commits (mirrored to a subversion repository) with commit messages and
links to the actual diff that went into CVS.
The link under "Recent CVS commits" is to localhost instead of
trac.gnugo.org at the moment.
Well, I'm probably partial, so please voice any concerns. However, I'm
strongly of the opinion that we should get rid of the extra work
involved in maintaining patches.html with lists of patches.
It's fine with me, but I suggest that you put a link inside
patches.html to trac.gnugo.org, with clear instructions on how to
view the last patches (for instance, I believe "Recent CVS commits"
is a more technical wording than "Last changes to GNU Go sources" and
may be less easy for newcomers).
Stéphane
... /// ... \\\ ...
_______________________________________________
gnugo-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnugo-devel
