Git Migration: github with svn access

Frank H. Ellenberger frank.h.ellenberger at
Sat Aug 11 04:08:26 EDT 2012

Hi Reuben,

Am 11.08.2012 09:55, schrieb Reuben Cummings:
> On Sat, Aug 11, 2012 at 10:49 AM, Frank H. Ellenberger
> <frank.h.ellenberger at> wrote:
>> Where is the Problem? ;-)
>> Frank
> Yes, I have read that. Look at the directions for sending a patch and
> notice the comment that forking github projects doesn't work. Compare
> that to the widespread github work-flow of forking a repo, committing
> changes, and then submitting a pull request. The latter is *much* more
> user friendly than manually creating patches, logging into bugzilla,
> filling a bug, submitting a patch...

Because of the
first time you should send your patches via bugzilla.

When I tested git, it was easy really easy to submit patches.
But in between, because I prefer revision numbers over hashes, I stick
with svn. Once configured in also
easy to use.


More information about the gnucash-devel mailing list