diff options
| author | Olav Vitters <ovitters@src.gnome.org> | 2008-02-08 14:37:30 +0000 |
|---|---|---|
| committer | Olav Vitters <ovitters@src.gnome.org> | 2008-02-08 14:37:30 +0000 |
| commit | bb8e9e64f5738df624848dd8bfae0f2577d52abd (patch) | |
| tree | 080e71687e245254dcb1ecd9c02e5d69a4281e31 | |
| parent | 97b7f15a5904cfe08a037e2e310dc659102e45e0 (diff) | |
| download | nautilus-bb8e9e64f5738df624848dd8bfae0f2577d52abd.tar.gz | |
Change CVS things into SVN.
* HACKING: Change CVS things into SVN.
svn path=/trunk/; revision=13712
| -rw-r--r-- | ChangeLog | 4 | ||||
| -rw-r--r-- | HACKING | 18 |
2 files changed, 13 insertions, 9 deletions
@@ -1,3 +1,7 @@ +2008-02-08 Olav Vitters <olav@bkor.dhs.org> + + * HACKING: Change CVS things into SVN. + 2008-02-08 Alexander Larsson <alexl@redhat.com> * libnautilus-private/nautilus-desktop-link.c: @@ -1,14 +1,14 @@ Hacking on Nautilus ------------------- -The Nautilus source tree is available from GNOME cvs (cvs.gnome.org) and +The Nautilus source tree is available from GNOME svn (svn.gnome.org) and in releases on the GNOME FTP site (http://ftp.gnome.org/pub/GNOME/sources/nautilus/). If you plan to hack on Nautilus, please make sure you work from the -CVS version. The CVS version can be checked from the GNOME cvs server. -See http://developer.gnome.org/tools/cvs.html for details on how to get -started with GNOME CVS. +SVN version. The SVN version can be checked from the GNOME svn server. +See http://developer.gnome.org/tools/svn.html for details on how to get +started with GNOME SVN. If you want to contribute in development discussions, please send mail to the nautilus mailing list: <nautilus-list@gnome.org>. Archives and @@ -23,11 +23,11 @@ If you've been working on a change to Nautilus and want to propose it for inclusion, you have to generate a patch and submit it for review by the maintainers. -Patches should be made with 'cvs diff -pu >patch' and should conform to -Nautilus coding style as described in docs/style-guide.html. We are -pretty strict about coding style, so please make sure you follow the -style guide to avoid unnecessary work on both sides when reviewing the -patch. +Patches should be made with 'svn diff --diff-cmd diff -x -up >patch' +and should conform to Nautilus coding style as described in +docs/style-guide.html. We are pretty strict about coding style, so +please make sure you follow the style guide to avoid unnecessary +work on both sides when reviewing the patch. The best way to submit a patch for review is to post it on the mailing list. That way everyone sees it and can take part in the following |