title: Can you do hg clone without getting default path?
body: <p>BRIEF:</p>
  
  <p>hg clone creates path "default" in /.hg/hgrc, set to where you cloned from.</p>
  
  <p>Q: is it possible to disable this automatically?</p>
  
  <p>DETAIL:</p>
  
  <p>This is already partially answered.</p>
  
  <p>In <a href="https://stackoverflow.com/questions/3302058/can-you-prevent-default-push-but-allow-pull">Can you prevent default-push, but allow pull?</a> we see how to set default-push, in some hgrc file such as /.hg/hgrc, or (my preference), in ~/.hgrc</p>
  
  <p>In <a href="https://stackoverflow.com/questions/6944981/is-hg-clone-equivalent-to-hg-initpull">Is hg clone equivalent to hg (init→pull)</a>
  Tim Henigan says that hg clone = init; pull; hg update default; setting up default path in /.hg/hgrc.</p>
  
  <p>Although elsewhere we see that this is not quite true.  hg clone may differ, e.g., in that it does hard link sharing.  Lacking an official statement of equivalence...</p>
  
  <p>Now, disabling default-push  helps a lot.</p>
  
  <p>But... I have fallen into the habit of doing "hg push default".  Which somewhat defaets the p;urpose.</p>
  
  <p>By the way: reason I am doing this, wanting to disable the default: workflow that goes master->workspace->staging_area->master. I do many clones of the master. Modifying /.hg/hgrc to edit [path] default each time I do a cline is a pain.  Doing "hg push" or "hg push default" in any of the workspaces can be bad. Instead I need to push to the staging area, ad only from the staging area am I allowed to push to the master.</p>
  
  <p>(I have tried master&lt;->staging_area&lt;->workspace, i.e. always cloning from the sdtaging area.  But I found this confusing.  Plus, the part that I haven't said yet: my project makes me delete or collapse history, which adds an additional level of confusion and error-prone-ness.)</p>