Changes between Version 9 and Version 10 of UsingPidginMercurial


Ignore:
Timestamp:
07/01/12 01:18:01 (7 years ago)
Author:
MarkDoliner
Comment:

We're using Mercurial now, so make this present tense instead of future tense

Legend:

Unmodified
Added
Removed
Modified
  • UsingPidginMercurial

    v9 v10  
    11= Using Pidgin Mercurial =
    2 This page is intended to house documentation for using Pidgin's Mercurial repositories once we switch from Monotone to Mercurial.
     2The master copy of the source code for libpurple, Pidgin, Finch, http://pidgin.im/, and http://imfreedom.org/ resides in [http://mercurial.selenic.com/ Mercurial] repositories.
    33
    44== Background ==
     
    66
    77== Anonymous Pull (Non-Developers) ==
    8 All Pidgin Mercurial repositories will be available via HTTP from [http://hg.pidgin.im http://hg.pidgin.im].
     8All Pidgin Mercurial repositories are available via HTTP from [http://hg.pidgin.im http://hg.pidgin.im].
    99
    1010== Developers ==
    1111
    1212=== Configure Mercurial ===
    13 Mercurial uses an rc file to control its configuration.  There are several that will affect your use.  One set of them is in `/etc/mercurial` and will be controlled by your package manager.  The others are entirely under your control.  Each repository has its own `hgrc` file in `repository/.hg/hgrc` which can be used to configure mercurial's behavior when interacting with that repository.  Finally, there is `~/.hgrc`, which will configure mercurial's behavior for any repository your user account touches.
     13Mercurial uses an rc file to control its configuration.  There are several that affect your use.  One set of them is in `/etc/mercurial` and is controlled by your package manager.  The others are entirely under your control.  Each repository has its own `hgrc` file in `repository/.hg/hgrc` which can be used to configure Mercurial's behavior when interacting with that repository.  Finally, there is `~/.hgrc`, which affects Mercurial's behavior for any repository your user account touches.
    1414
    15 When working with Pidgin's mercurial repositories, we expect that you will have at least a minimum configuration that gives your name in the 'First Last <email@address.tld>' format.  To do that, two simple lines need to be inserted into an appropriate `hgrc` (I believe most people will want to do this in `~/.hgrc`):
     15When working with Pidgin's Mercurial repositories, we expect you to have at least a minimum configuration that gives your name in the 'First Last <email@address.tld>' format.  To do that, two simple lines need to be inserted into an appropriate `hgrc` (I believe most people will want to do this in `~/.hgrc`):
    1616{{{
    1717[ui]
     
    1919}}}
    2020
    21 Other useful options that can be set in the `[ui]` section of an `hgrc` are the merge tool and to make mercurial verbose or not:
     21Other useful options that can be set in the `[ui]` section of an `hgrc` are the merge tool and to make Mercurial verbose or not:
    2222{{{
    2323[ui]
     
    6363
    6464=== Access Control ===
    65 Access control on Pidgin's Mercurial server is strict.  The repositories will be structured like so (developers/CPW's listed here are for the purpose of example):
     65Access control on Pidgin's Mercurial server is strict.  The repositories are structured like so (developers/CPW's listed here are for the purpose of example):
    6666
    6767{{{
    6868hg.pidgin.im          # Mercurial server
    6969 + pidgin               # "Official" Pidgin and libpurple repositories
    70  |  + main                # replaces im.pidgin.pidgin in Monotone
    71  |  + 2_x_y               # replaces im.pidgin.pidgin.2.x.y in Monotone
     70 |  + main                # replaced im.pidgin.pidgin in Monotone
     71 |  + 2_x_y               # replaced im.pidgin.pidgin.2.x.y in Monotone
    7272 + dev                  # Developers' repositories
    7373 |  + darkrain            # for all repositories darkrain wishes to create
    74  |  |  + irc                # replaces im.pidgin.cpw.darkrain42.irc in Monotone
    75  |  |  + xmpp_roster        # replaces im.pidgin.cpw.darkrain42.xppp.roster in Monotone
     74 |  |  + irc                # replaced im.pidgin.cpw.darkrain42.irc in Monotone
     75 |  |  + xmpp_roster        # replaced im.pidgin.cpw.darkrain42.xppp.roster in Monotone
    7676 |  + rekkanoryo          # for all repositories rekkanoryo wishes to create
    77  |     + examples           # replaces im.pidgin.cpw.rekkanoryo.examples in Monotone
     77 |     + examples           # replaced im.pidgin.cpw.rekkanoryo.examples in Monotone
    7878 + cpw                  # Crazy Patch Writers' repositories
    7979 |  + eionrobb            # for all repositories eionrobb wishes to create
     
    9292}}}
    9393
    94 Access control will be as follows:
     94Access control is as follows:
    9595  * Developers have write access to `pidgin/*`
    9696  * Developers can create and modify repositories in `dev/$NICKNAME/`
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!