Bill and Bernhard,
My changes are largely incorporated into Bill's, see:
http://grasshopper.grasshoppernet.com/~bhughes/
Mails to the Baylor Address about several issues were never answered.
Bill told me that he also never got an answer from the developers.
The webstructure on Baylor seems to be a bit off, and nobody seems
to care to link Bill's site from there.
The work was mentioned on the user list, too.
Markus Neteler then contacted us and AFAIK mentioned the B. Hughes'
patches to the Baylor developers, which at least partly seem to
incorporate them. But still no comment about that.
well, let´s start again. After discussion with Bruce I will
take care for your patches now. To distribute the workload
I suggest that we stay in contact about including your patches
into the 5.0 code. I keep the line to Baylor then. Would that be o.k
with you?
Generally speaking:
If you (the GRASS community) have patches, please send them to
ftp://keck.baylor.edu/pub/grass/incoming/
For our small team it is rather time consuming to search for patches
on the net ourselves. Therefore we kindly request you to upload
files to the GRASS ftp-Server. Please send an announce email as well.
We urgently need more support in GRASS development and programming.
Migrating all the 4.2.1 modules to 5.0 data structures is quite a
big job... Beside the (voluntary) work on GRASS we have to work on
projects etc. Therefore support is very welcome.
Thank you very much
Markus Neteler
On Fri, Jun 04, 1999 at 10:37:08AM +0100, Markus Neteler wrote:
well, let´s start again. After discussion with Bruce I will
take care for your patches now. To distribute the workload
I suggest that we stay in contact about including your patches
into the 5.0 code. I keep the line to Baylor then. Would that be o.k
with you?
Yes.
I just wanted to explain how the situation developed, when I started
to do some GRASS patching.
Generally speaking:
If you (the GRASS community) have patches, please send them to
ftp://keck.baylor.edu/pub/grass/incoming/
I found out about that later.
I recommend replacing the Bayler GRASS 5.0b page(s) with one page,
linking to all GRASS5.0b information as quick as possible.
And just throw any link in, you find. Maintaining this is not
very time consuming.
For our small team it is rather time consuming to search for patches
on the net ourselves. Therefore we kindly request you to upload
files to the GRASS ftp-Server. Please send an announce email as well.
True. Like I said, mail was send, but there was no developers response,
back then.
Unfortunatly Bill told me that he cannot work on GRASS over the summer
and I have no current plans on hacking GRASS for a while.
But you never know, this might change next week so it very good to know
where the patches have to go now!
Bernhard
Markus Neteler wrote:
Generally speaking:
If you (the GRASS community) have patches, please send them to
ftp://keck.baylor.edu/pub/grass/incoming/
For our small team it is rather time consuming to search for patches
on the net ourselves. Therefore we kindly request you to upload
files to the GRASS ftp-Server. Please send an announce email as well.
We urgently need more support in GRASS development and programming.
Migrating all the 4.2.1 modules to 5.0 data structures is quite a
big job... Beside the (voluntary) work on GRASS we have to work on
projects etc. Therefore support is very welcome.
I don't know if thing have changed, but AFAIK, there is no "programmer's
manual" for grass5.0 describing the new structure. That is the main
reason for I didn't port anything to grass5.0 yet, including m.in.e00,
which would hence be enhanced and import floating values' A/I grid
rasters.
--
Michel Wurtz ENGEES - CEREG
1, quai Koch - BP 1039, F-67070 STRASBOURG cedex
Tel: +33 03.88.24.82.45 Fax: +33 03.88.37.04.97