Geert Janssens wrote > > On 13-08-12 11:33, reubano wrote: >> reubano wrote >>> On Sat, Aug 11, 2012 at 9:34 PM, Derek Atkins <warlord@> >>> wrote: >>>> Reuben Cummings <reubano@> writes: >>>> >>>> Gnucash is following the Gnome patch submission practice. Gnome uses >>>> git, >>>> but not Github, and >>>> doesn't use pull requests (which are actually designed to work through >>>> email with, guess what, git >>>> format-patch). I hope that even after we migrate to git we'll continue >>>> with the same submission >>>> practice. >>> Is there any way both could work together? I've been reading a bit on >>> the shortcomings of GitHub PRs [1] and am curious if any combination >>> of git-request-pull [2], .patch URL [3], or patches-by-email [4] could >>> work. >>> >>> [1] https://github.com/torvalds/linux/pull/17#issuecomment-5654674 >>> [2] http://git-scm.com/docs/git-request-pull >>> [3] https://help.github.com/articles/using-pull-requests/ (Patch and >>> Apply section) >>> [4] >>> http://alblue.bandlem.com/2011/12/git-tip-of-week-patches-by-email.html >>> >> I also just read about git-bz [1] (linked from the git wiki). It looks >> promising as well. If there was some way to integrate OAuth it seems like >> it >> could even be ideal. Thoughts? >> >> [1] http://wiki.gnucash.org/wiki/Git-bz >> > Git-bz does look useful to me. People that want to submit patches > without having commit access can install this locally. At first sight it > doesn't seem to create new bugs if the patch you wish to publish is not > related to an existing bug. That may be a drawback. > > Geert >
PyBugz[1] may do the trick [1] https://github.com/williamh/pybugz -- View this message in context: http://gnucash.1415818.n4.nabble.com/Git-Migration-tp3996329p4656355.html Sent from the GnuCash - Dev mailing list archive at Nabble.com. _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
