[GRASS-dev] Re: r.out.gdal segfault in XY location
tutey at o2.pl
Mon Nov 6 02:46:06 EST 2006
> Maciej Sieczka wrote:
>>> PS: If I understand well -- patches should be submitted to Gforge in
>>> the future and not sent as the attachment to the grass-dev list,
>> That's how I imagine this. Is that OK for devs?
> probaby depends on the size of the patch. For a few lines it's probably
> not worth the trouble of using the patch tracker. For larger patches and
> module submission it is more appropriate than sending 50kb emails to the
> entire list.
IMO, the main reason to use the tracker instead of sumbitting patches
just to the dev list is to keep the track of them :). So that we can
easilly access the patches that have been sent half a year ago, and
were ignored then, but now they could be usefull. For this, I believe,
any patch should be submitted by the user to the tracker, instead of
the list directly (the message will be forwarded to the list from the
tracker anyway). Once it is apllied (or used as a protype for another
patch), it's ticket should be closed.
> Say, could a tracker hold Wiki Add-ons scripts & modules? I always worry
> that old scripts will be lost when people switch ISPs, jobs, graduate,
We could have a separate tracker for this, or use the the GForge ftp
space (there is such thing).
What is file size limit and the overall quota, in the tracker and the
ftp space? Better ideas?
More information about the grass-dev