Home Specs Ideas Testing About
You are here: CSS Working Group Wiki » CSSWG Tools » Quick Guide To Using Mercurial

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tools:hg [2014/12/30 22:54] – [Setting Up Mercurial Preferences] plinsstools:hg [2017/01/30 16:55] (current) – plinss
Line 56: Line 56:
   mq =    mq = 
   graphlog =    graphlog = 
 +  progress =
 +  bookmarks =
 +  color =
      
   [auth]   [auth]
Line 97: Line 100:
 ** Avoiding Fingerprint Warnings (and improving security)** ** Avoiding Fingerprint Warnings (and improving security)**
  
-Depending on your OS and Mercurial root certificate configuration you may get a warning message about the host certificate when communicating with the central repository. If that happens, you can remove those warnings by adding the following to your configuration file: +Depending on your OS and Mercurial root certificate configuration you may get a warning message about the host certificate when communicating with the central repository. If that happens, please see [[https://www.mercurial-scm.org/wiki/CACertificates#Configuration_of_HTTPS_certificate_authorities|the instructions on the Mercurial wiki]].
-  [hostfingerprints] +
-  dvcs.w3.org = 14:A5:F7:99:95:F8:41:9B:02:71:2C:4B:87:D2:E0:8B:F2:CF:4B:A3 +
-  hg.csswg.org = 71:06:B1:F3:E4:74:AB:53:C2:CE:8E:BF:99:7D:F8:B4:4C:22:E8:B9 +
-  hg.fxtf.org = B9:28:66:37:CB:36:3E:0B:A6:05:32:2F:7A:34:76:54:29:37:2A:9D +
-  hg.css-houdini.org = 20:92:CF:9D:D7:29:C6:B8:7D:58:E3:1D:A9:42:C6:9C:9F:02:87:49 +
- +
-Note that these fingerprints will only be valid until the certificates expire (dvcs.w3.org expires 03-may-2016, hg.csswg.org expires expires 10-apr-2016). You will need to update the fingerprints when new certificates are issued. +
- +
-Alternatively (and better if you're on an OS where this is easy), you can avoid ever having to add fingerprints by following [[http://mercurial.selenic.com/wiki/CACertificates#Configuration_of_HTTPS_certificate_authorities|the instructions on the Mercurial wiki]].+
 </note> </note>
    
Line 140: Line 134:
 </code> </code>
  
-** Resources directory (needed when authoring script tests using testharness) **+** Resources directory (for script tests) ** 
 + 
 +This directory contains testharness.js which is needed if you'll be running script tests locally. This is maintained in a separate repository in GitHub. See the [[https://help.github.com/articles/set-up-git/|instructions on GitHub]] for setting up git, then:
 <code> <code>
 cd /     #not required, but resources directory is located at root level in repository cd /     #not required, but resources directory is located at root level in repository
-hg clone https://dvcs.w3.org/hg/resources/     +git clone https://github.com/w3c/testharness.js.git resources
 </code> </code>
  
-** CSSWG Spec Repository **+** CSSWG Draft Repository **
 <code> <code>
-cd /mirror/hg/dvcs.w3.org/   #just an example, pick your own local directory +cd /mirror/hg.csswg.org/   #just an example, pick your own local directory 
-hg clone https://dvcs.w3.org/hg/csswg/+hg clone https://hg.csswg.org/drafts/
 </code> </code>
  
-** FXTF Spec Repository **+** FXTF Draft Repository **
 <code> <code>
-hg clone https://dvcs.w3.org/hg/FXTF/ +hg clone https://hg.fxtf.org/drafts/ 
 </code> </code>
  
Line 166: Line 162:
 Note: By default, the working directory name will match the name of the central repository on the server (the last path component of the URL). If you want to use a different name for your working directory, enter it at the end of the clone command, e.g.: Note: By default, the working directory name will match the name of the central repository on the server (the last path component of the URL). If you want to use a different name for your working directory, enter it at the end of the clone command, e.g.:
 <code> <code>
-hg clone https://dvcs.w3.org/hg/csswg/ specs+hg clone https://hg.csswg.org/drafts/ csswg
 </code> </code>
  
Line 173: Line 169:
 All of our repositories are readable by anyone. Permission to write (i.e. push) into the repositories is restricted to certain users. All of our repositories are readable by anyone. Permission to write (i.e. push) into the repositories is restricted to certain users.
  
-Access to the CSSWG Test Suite Repository is based on your account for [[http://test.csswg.org/shepherd/|Shepherd]] and this wiki (user accounts are shared between systems). By default, all CSSWG members should have write access. Other contributors to the Test Suite Repository need to ask for access. If you already have an account on this wiki, log in to Shepherd and submit a request to modify assets on the [[https://test.csswg.org/shepherd/login/account/access/|Repository Access]] page. You will receive an email once repository access has been granted. If you don't already have an account, you can [[https://test.csswg.org/shepherd/register/|register for an account on Shepherd]].+Access to the repositories on hg.csswg.org, hg.fxtf.org, and hg.css-houdini.org is based on your account for [[http://test.csswg.org/shepherd/|Shepherd]] and this wiki (user accounts are shared between systems). By default, all CSSWG members should have write access to the Test Suite Repository. Other contributors to the Test Suite Repository need to ask for access. If you already have an account on this wiki, log in to Shepherd and submit a request to modify assets on the [[https://test.csswg.org/shepherd/login/account/access/|Repository Access]] page. You will receive an email once repository access has been granted. If you don't already have an account, you can [[https://test.csswg.org/shepherd/register/|register for an account on Shepherd]].
  
-Access to the CSSWG or FXTF Spec Repositories is controlled by your W3C user account. All CSSWG members should have write access to the CSSWG Spec Repository, all CSSWG and SVGWG members should have write access to the FXTF Spec Repository. If you're not a member of the appropriate group and need write access, please email [[mailto:peter.linss@hp.com|Peter]].+In addition to the Test Suite Repository, all CSSWG members should have write access to the CSSWG Draft Repository, all CSSWG and SVGWG members should have write access to the FXTF and CSS-Houdini TF Draft Repositories. If you need write access and don't already have it, you can submit a request on the [[https://drafts.csswg.org/login/account/access/|CSSWG Repository Access]], [[https://drafts.fxtf.org/login/account/access/|FXTF Repository Access]], or [[https://drafts.css-houdini.org/login/account/access/|CSS-Houdini TF Repository Access]] pages. 
 + 
 +Access to the repositories on dvcs.w3.org is controlled by your W3C user account. If you're not a member of the appropriate group and need write access, please email [[mailto:peter.linss@hp.com|Peter]] or [[mailto::sysreq@w3.org|sysreq]].
  
 ===== Working With Mercurial ===== ===== Working With Mercurial =====
Line 325: Line 323:
  
 At this point your changes will be available on the server to other users. At this point your changes will be available on the server to other users.
 +
 +
 +:?: If you see a message similar to: "abort: authorization failed", then email Peter. See Footer at bottom.
 +
  
 === Merging Branches of Work: hg merge === === Merging Branches of Work: hg merge ===
Line 518: Line 520:
  
 Use ''hg help'' to learn more about each command. Use ''hg help'' to learn more about each command.
 +
 +If you need to edit history, e.g. undo/drop your latest change set, see:
 +  * http://mercurial.selenic.com/wiki/EditingHistory
 +In particular, ''hg strip'' is useful for dropping the most recent changeset.
  
 ===== CVS / Subversion Cheat Sheet ===== ===== CVS / Subversion Cheat Sheet =====
 
tools/hg.1420008857.txt.gz · Last modified: 2014/12/30 22:54 by plinss
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki