Re: [galaxy-dev] patch contribution (was Re: So I think I fixed a bug.)

2012-08-29 Thread John Chilton
Great, I am glad it was useful. Renaming the repository isn't needed, especially if you just have one pull request open at a time. But there have been times I have had maybe 4 or 5 open pull requests at once, so then it helps to keep track of which repository maps to which feature or bug fix. If

Re: [galaxy-dev] patch contribution (was Re: So I think I fixed a bug.)

2012-08-28 Thread Clare Sloggett
Hi John, Thank you, this is really useful! I don't understand the purpose of renaming the repository to galaxy-central-new-feature - what does this achieve? I'm pretty new to mercurial and more familiar with git, so that could be why I'm confused. Thanks, Clare On 24 August 2012 00:07, John

[galaxy-dev] patch contribution (was Re: So I think I fixed a bug.)

2012-08-23 Thread Langhorst, Brad
Maybe I'm just doing it wrong… but I find it unusually difficult to put together a coherent pull request without doing a dedicated repo clone. maybe somebody who knows a good way to submit pull requests could populate this wiki page? http://wiki.g2.bx.psu.edu/Develop/Mercurial brad On Aug 23,

Re: [galaxy-dev] patch contribution (was Re: So I think I fixed a bug.)

2012-08-23 Thread John Chilton
I don't know that difficult is the right word, I would call the process heavy handed and time consuming, especially relative to similar git workflows. I have heard the Galaxy developers say on multiple occasions the prefer pull requests coming using a dedicated clone though and this makes a lot of