changeset 50:69d74942fb47

The easy way: direct pull from a shared file system.
author Martin Geisler <mg@daimi.au.dk>
date Sun, 24 Feb 2008 10:57:10 +0100
parents ebb71e2f8222
children 7b10f2193026
files doc/development.txt
diffstat 1 files changed, 7 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/doc/development.txt	Sun Feb 24 10:53:57 2008 +0100
+++ b/doc/development.txt	Sun Feb 24 10:57:10 2008 +0100
@@ -38,8 +38,13 @@
 --------------------
 
 When you have created a new feature or fixed a bug, then you need to
-send your changes to one of the VIFF developers. The patchbomb_
-extension for Mercurial will allow you to use
+send your changes to one of the VIFF developers. If you share a file
+system with one of the developers, then the easiest way to get your
+changes back into VIFF is to ensure that one of the developers has
+read access on the repository files. He can then simply pull the
+changesets over and eventually push them out to the VIFF repository.
+
+The patchbomb_ extension for Mercurial will allow you to use
 
 .. sourcecode:: text