Databases
StackOverflow2013
Postsdbo
POHow to manage an open-source project using mercurial and Google Code?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to manage an open-source project using mercurial and Google Code?
    text
    copied!<p>I have an open source project hosted on Google Code using Mercurial. It works great for me, i generally love mercurial.</p> <p>I have several community members who clone my project, make changes to their clone, and periodically like to send me patches. These contributors do not have commit access to the master repository, aka the <a href="http://help.github.com/send-pull-requests/" rel="noreferrer">"Fork + Pull"</a> model.</p> <p>We haven't really found a good way for them to send me contributions. If they have the foresight to put all of their changes for a given feature onto a named branch in their clone, it's easy for me to pull just those changes into the master. However, they often don't have that foresight since many of these changes start out as local tinkering on their default branch.</p> <p>Another alternative is to mail around diffs using <code>hg export</code> and <code>hg import</code>, but that seems rather 1974.</p> <p>It's possible there may be an answer somewhere in mercurial queues, but that's always seemed like a feature oriented toward "power users", and many of my devs may be experts with git but are complete n00bs when it comes to hg. We're still trying to get unnamed branch merging down, I'm loath to encourage them to play around with something that complicates the mental model even further, especially when I know so little about the subject.</p> <p>I feel like I must be going about this wrong. Github seems to have a good story for this with its concept of pull requests. What's the best way to accept contributions from community members when using mercurial on google code?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload