I've expanded on the documentation for v.to.points, explaining the -v and -i
flags better. Can someone check this and upload to cvs if it's ok? This is
my first attempt at improving documentation, so any pointers would be
welcome.
Is there an easier way to get man page upgrades into a queue for developer
review rather than just bombarding 2 or 3 people with email attachments?
I've had trouble getting cvs write access configured properly in the past,
so I'm looking for simpler way.
On Fri, Aug 25, 2006 at 03:28:50PM -0300, Patton, Eric wrote:
I've expanded on the documentation for v.to.points, explaining the -v and -i
flags better. Can someone check this and upload to cvs if it's ok? This is
my first attempt at improving documentation, so any pointers would be
welcome.
Is there an easier way to get man page upgrades into a queue for developer
review rather than just bombarding 2 or 3 people with email attachments?
I've had trouble getting cvs write access configured properly in the past,
so I'm looking for simpler way.
Is there an easier way to get man page upgrades into a queue for
developer review rather than just bombarding 2 or 3 people with email
attachments? I've had trouble getting cvs write access configured
properly in the past, so I'm looking for simpler way.
Please send them to the bug tracker. Be careful about pasting
attachments (diffs) into the web based front end as it will wrap the
text and break the patch. email them to the bug tracker directly instead
(see below). If stuff is only sent to the mailing lists, it could easily
be lost in the noise if someone isn't around to act on it immediately.
PS - Maciek, this patch may address BT #2802.
you can add info to a bug by adding e.g. [bug #2802] to the email's
subject line and cc'ing it to grass-bugs (at) intevation.de
An email there without a bug number in the subject line will create a
new bug report.