Changes between Version 16 and Version 17 of Submitting/General


Ignore:
Timestamp:
Dec 4, 2019, 12:01:39 AM (4 months ago)
Author:
wenzeslaus
Comment:

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

Legend:

Unmodified
Added
Removed
Modified
  • Submitting/General

    v16 v17  
    1414   * Vector maps are always considered completely.
    1515
    16 == Submitting code to SVN ==
    17 
    18 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`:
    19 
    20 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.
    21 
    22 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`.
     16== Submitting code ==
     17
     18Be 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.
    2319
    2420=== Commit messages ===
     
    8177(commit messages are not for opening discussions or general communication)
    8278}}}
     79
     80=== Creating (legacy) diffs ===
     81
     82Be 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.
     83
     84Such 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`.
    8385
    8486=== SVN Properties ===