On May 19, 2012, at 10:09 AM, Peter van Heusden wrote: > Hi there > > As I adapt Galaxy to the needs of the particular workflows I'm > implementing, I invariably end up "tweaking" the existing code, > especially the tool definitions and the datatypes config file. These > tweaks are often minor - e.g. adding an extra parameter to Ross Lazarus' > ClustalW's code, changing the way the binary is called (e.g. clustalw2 > on ubuntu is installed as clustalw, BLAST+ is installed single threaded > so the -num_threads option in the ncbi_blastn_wrapper.xml doesn't work), > but > > a) Sometimes they make sense to share with the rest of the Galaxy community > b) local changes make it more tricky to keep in sync with upstream > changes to Galaxy > > What's the best procedure for proposing changes up upstream galaxy? > Posting patches to galaxy-dev? Is there some mercurial magic that can help? > > Thanks, > Peter
Hi Peter, The best way is to fork Galaxy and use a pull request in bitbucket. Thanks! --nate > > ___________________________________________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > > http://lists.bx.psu.edu/ ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
