Changes between Version 37 and Version 38 of UsingPidginMonotone

Timestamp:

Oct 16, 2008, 5:51:12 PM (15 years ago)

Author:

elb

Comment:

--

UsingPidginMonotone

@@ -15 +15 @@
 == Getting Started with Pidgin monotone ==
 
-There is a monotone server running on pidgin.im.  Its key fingerprint is {{{42a055d77e641de411e118d121cfc598ec0e7725}}}.
+There is a monotone server running on mtn.pidgin.im.  Its key fingerprint is {{{42a055d77e641de411e118d121cfc598ec0e7725}}}.
 
 The initial revision history retrieval is quite taxing on the server.  In order to make the initial pull more efficient, we provide a snapshot of the mtn database to bootstrap the process.  '''This database requires monotone 0.36 or newer.'''
@@ -30 +30 @@
   $ bzip2 -d pidgin.mtn.bz2
 
-  $ mtn -d $DATABASE pull --set-default pidgin.im "im.pidgin.*"
+  $ mtn -d $DATABASE pull --set-default mtn.pidgin.im "im.pidgin.*"
   $ mtn -d $DATABASE co -b im.pidgin.pidgin $WORKINGDIR
 }}}
@@ -36 +36 @@
 If you get this message:
 {{{
-    $ mtn -d $DATABASE pull --set-default pidgin.im "im.pidgin.*"
+    $ mtn -d $DATABASE pull --set-default mtn.pidgin.im "im.pidgin.*"
     mtn: misuse: database /home/user/monotone_databases/pidgin.mtn is laid out according to an old schema
     mtn: misuse: try 'mtn db migrate' to upgrade
@@ -50 +50 @@
 (The variables here are just to help you understand which parts of the process are up to your personal choice.)
 
-This will create a database for storing your development stuff, fetch the entire revision history available from pidgin.im to that database, and then check out a working copy of the newest revision of Pidgin in that database.  To update the database from the server in the future, you can either a) simply go to {{{$WORKINGDIR}}} and execute {{{mtn pull}}}, or execute {{{mtn -d $DATABASE pull}}} from anywhere.  Note that this will pull the new revision ''history'' from the server, but will not update your working directory to reflect the newest available revision.  For this, you need to run {{{mtn up}}} in {{{$WORKINGDIR}}}.
+This will create a database for storing your development stuff, fetch the entire revision history available from mtn.pidgin.im to that database, and then check out a working copy of the newest revision of Pidgin in that database.  To update the database from the server in the future, you can either a) simply go to {{{$WORKINGDIR}}} and execute {{{mtn pull}}}, or execute {{{mtn -d $DATABASE pull}}} from anywhere.  Note that this will pull the new revision ''history'' from the server, but will not update your working directory to reflect the newest available revision.  For this, you need to run {{{mtn up}}} in {{{$WORKINGDIR}}}.
 
 Consult the monotone documents, and particularly [http://venge.net/monotone/docs/CVS-Phrasebook.html#CVS-Phrasebook their CVS phrasebook] to see the things you can now do with your database and working copy.  You should find that most of the actions at this point feel pretty familiar.