Notification mails for git repos

Geert Janssens janssens-geert at
Thu Jan 31 02:37:14 EST 2013

On 31-01-13 04:44, John Ralls wrote:
> On Jan 30, 2013, at 3:01 PM, Yawar Amin <yawar.amin at> wrote:
>> Hi Mike,
>> On 2013-01-30, at 16:49, Mike Alexander <mta at> wrote:
>>> [...]
>>> The article says to use bisect to find the first revision that introduced the bug, but with a project as big as GnuCash, where some bugs have been around for years, that would be painful.
>> Actually, you don't need to use bisect if you don't want to. Let me give you an example. Say you want to fix a bug for both trunk and 2.4. All you have to do is checkout the last common commit on which both trunk and 2.4 are based, and fix the bug on top of that. (Of course I'm assuming the bug is present in both branches. But presumably you've already established that.) Then merge into trunk and 2.4.
>> We can make it even simpler to find these branch-common commits just by tagging them.
>> Bisecting is a nice luxury but you don't need it....
> Yawar,
> 2.4 was branched off of 2.3, not trunk.
This is not correct. From 2.4.0 until 2.4.4, trunk and the 2.4 branch 
were the same. 2.4 was only branched after 2.4.4.


More information about the gnucash-devel mailing list