[GRASS-dev] GRASS at GForge first steps
jachym.cepicky at centrum.cz
Mon Nov 6 13:04:30 EST 2006
great work, Maciek. One question from my side:
On Sat, Nov 04, 2006 at 04:17:03PM +0100, Maciej Sieczka wrote:
> Patches tracker is for storing and managing the patches candidates
> (both code and docs). Currently, they are often sent to dev list. If
> they are not reacted upon quickly, or too intrusive to be applied right
> away but valuable for future developmement, they happen to be
> forgotten. The tracker might help us to manage them in a convenient
> way. Jachym volunteered to maintain the code patches submitted. Thanks
> Jachym! Is there somebody willing to take care of docs submitted?
I will do it (try to do it). What exactly am I supposed to do? My
imaginatio is following:
- Someone will submit some patch to wald
- I (or someone else) will examine the patch, look if it does what
it is supposed to do and paste my comment about this patch to
- If it will be only small correction, I'll apply the patch to CVS
- If it will be bigger change and nobody will complain in grass-dev
within a week or so, I'll commit the change too.
Anything else? Or do I understand this task completely wrong?
e-mail: jachym.cepicky at centrum.cz
Department of Geoinformation Technologies
613 00, Brno
e-mail: xcepicky at node.mendelu.cz
Tel.: +420 545 134 514
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: Digital signature
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20061106/7676abb7/attachment.bin
More information about the grass-dev