Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 13 and Version 14 of UsingPidginMonotone


Ignore:
Timestamp:
Apr 9, 2007, 12:22:37 AM (17 years ago)
Author:
rlaager
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UsingPidginMonotone

    v13 v14  
    1010== Getting Started with Pidgin monotone ==
    1111
    12 There is currently an experimental monotone server running on pidgin.im, which fetches nightly changes from Gaim SVN (by way of [http://www.darcs.net/DarcsWiki/Tailor tailor]).  We may or may not keep this history going forward; for now the server is read-only, and intended to be simply a point for people to start playing.  Note that the read-only server does not mean you cannot commit -- this is one of the beautiful things about a DVCS.
     12There is a monotone server running on pidgin.im.
    1313
    1414To fetch the revision history from this server, and check out a working copy, do:
     
    2424(The variables here are just to help you understand which parts of the process are up to your personal choice.)
    2525
    26 This will create a database for storing your Gaim development stuffs, fetch the entire revision history available from pidgin.im to that database, and then check out a working copy of the newest revision of Gaim 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}}}.
     26This 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}}}.
    2727
    2828Consult 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.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!