[GRASS-dev] r.watershed2 with MFD

Glynn Clements glynn at gclements.plus.com
Fri Dec 5 21:05:25 EST 2008


Markus Metz wrote:

> BTW my nightmare is to screw up the svn history that's why I hesitate to
> submit directly to grass7 (or grass64).

The only thing that can really screw up the history is to make a local
copy, then add it to the repository as if it were new code. This not
only loses all prior history, but even the fact that it is a copy.

If you want to create a fork or clone of an existing module, use
"svn copy", not e.g. "cp -r". Also the source should be repository URL
rather than a working copy directory. E.g.:

cd raster
svn copy https://svn.osgeo.org/grass/grass/trunk/raster/r.watershed r.watershed.mfd

This way, you can merge the changes since the fork back into the
original. Or if you decide to replace the original with the forked
version, the fork will have inherited the original's history when it
was created.

grass-addons is part of the same repository as grass, so it's possible
to copy, rename, merge, etc between grass-addons and grass.

-- 
Glynn Clements <glynn at gclements.plus.com>


More information about the grass-dev mailing list