Notification mails for git repos

Yawar Amin yawar.amin at gmail.com
Wed Jan 30 12:27:17 EST 2013


Hi Geert,

On 2013-01-30, at 11:13, Geert Janssens <janssens-geert at telenet.be> wrote:

> [...]
> Alternatively I played with the idea to just drop the whole BP trickery.

Right idea....

> Instead we could use a backport branch in git. Each dev that commits something to trunk/master that should also be backported, could cherry-pick this commit to the backport branch.

See below for another way....

> [...]
> Any thoughts, bright ideas, suggestions ?

With a pure git solution, we can get rid of backporting and switch to daggy fixes (http://queue.acm.org/detail.cfm?id=1595636, section 'Daggy Fixes and Cherry-picking', near the end). Benefits: backporting will become simply merging; the dag will show us exactly where a fix was made and to which branches it was applied.

Regards,

Yawar


More information about the gnucash-devel mailing list