code review 1238044: Provide advice on using Mercurial Queues in conjunction...

doc/contribute.html

 <!-- Contributing to the Go project -->
 
 <h2 id="Introduction">Introduction</h2>
 
 <p>
 This document explains how to contribute changes to the Go project.
 It assumes you have installed Go using the
 <a href="install.html">installation instructions</a> and
 have <a href="code.html">written and tested your code</a>.
 (Note that the <code>gccgo</code> frontend lives elsewhere;
@@ skipping 85 matching lines @@
 <a href="#copyright">copyright purposes</a>.
 </p>
 
 <p>
 To help ensure changes are only created by <code>hg submit</code>,
 the code review extension disables the standard <code>hg commit</code>
 command.
 </p>
 
 <p>
-Mercurial power users: To allow Go contributors to take advantage of
-Mercurial's functionality for local revision control, it might be interesting
-to explore how the code review extension can be made to work alongside
-the Mercurial Queues extension.
+Mercurial power users: if you prefer to use the Mercurial Queues extension, see
+<a href="codereview_with_mq.html">Using Mercurial Queues with Codereview</a>.
 </p>
 
 <h3>Configure the extension</h3>
 
 <p>Edit <code>$GOROOT/.hg/hgrc</code> to add:</p>
 
 <pre>
 [extensions]
 codereview = YOUR_GO_ROOT/lib/codereview/codereview.py
 
@@ skipping 401 matching lines @@
 This rigmarole needs to be done only for your first submission.
 </p>
 
 <p>Code that you contribute should use the standard copyright header:</p>
 
 <pre>
 // Copyright 2010 The Go Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style
 // license that can be found in the LICENSE file.
 </pre>