Changes between Version 16 and Version 17 of Submitting/General

Timestamp:

12/04/19 00:01:39 (5 years ago)

Author:

wenzeslaus

Comment:

Remove Subversion from intro, assuming merge of PR 237 ​https://github.com/OSGeo/grass/pull/237

Submitting/General

@@ -14 +14 @@
    * Vector maps are always considered completely.
 
-== Submitting code to SVN ==
-
-Be sure to develop on top of the LATEST GRASS code (which is in our SVN repository). You can re-check before submission with `svn diff`:
-
-Be sure to create unified (`diff -u`) format. "Plain" diffs (the default format) are risky, because they will apply without warning to code which has been substantially changed; they are also harder to read than unified.
-
-Such diffs should be made from the top-level directory, e.g. `svn diff display/d.vect/main.c`; that way, the diff will include the pathname rather than just an ambiguous `main.c`.
+== Submitting code ==
+
+Be sure to develop on top of the *latest* GRASS GIS code which is in a Git repository on !GitHub. See [https://github.com/OSGeo/grass/blob/master/CONTRIBUTING.md CONTRIBUTING] file there.
 
 === Commit messages ===
@@ -81 +77 @@
 (commit messages are not for opening discussions or general communication)
 }}}
+
+=== Creating (legacy) diffs ===
+
+Be sure to create unified (`diff -u`) format. "Plain" diffs (the default format) are risky, because they will apply without warning to code which has been substantially changed; they are also harder to read than unified.
+
+Such diffs should be made from the top-level directory, e.g. `git diff display/d.vect/main.c`; that way, the diff will include the pathname rather than just an ambiguous `main.c`.
 
 === SVN Properties ===