Patch Manager (was Re: [Cp-tools-discuss] Getting Doc and Tag contexts)

[Alex Lancaster]

>>>>> "MW" == Mark Wielaard <address@hidden> writes:

MW> Hi, Is there a good way to get the Doc and Tag context?  To get a
MW> better idea where the remaining errors/warnings come from while
MW> generating documentation for Classpath I added the following patch
MW> which helps, but there might be a better way to get the context of
MW> a Tag or Doc.

Mark (and anybody else sending in those nice patches),

Thanks for the all patches!  It's great to see all this action on
classpath tools.  Just a request: could you start uploading these to
the savannah Patch Manager for cp-tools at:

 http://savannah.gnu.org/support/?group_id=508

Use the "upload patch" feature if you can, because it means that the
patch will be a self-contained file that can be copied to the local
CVS checkout and then applied directly either using "patch" from the
command line or the diff/patch mode in Emacs, which is what I use.
I've also added the categories "gjdoc", "texidoclet" and "other" so we
can easily collect the patches for the relevant module, so please
choose the relevant one.

This way we can easily keep track of all the patches for the project,
and see what still needs to be applied, at-a-glance, rather than
having to trawl through the e-mail archives to keep track of them all.
It also allows us one of us to take reponsibility for testing out
and/or applying the patch, so nobody will inadvertantly attempt to
apply the same patch twice or spend time testing the patch to discover
that somebody else is doing the same thing.  The Manager has been
set-up to also e-mail the list as soon a new patch is added and or any
existing one is updated or applied, so we end up with the best of both
worlds...

Cheers!

Alex
-- 
    Alex Lancaster * address@hidden * SourceForge Developer