Re: Multi-branch committing in git, revisited

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: David Christensen <david(at)endpoint(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Multi-branch committing in git, revisited
Date: 2010-09-22 03:35:12
Message-ID: 15394.1285126512@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> The problem is that the cherrypicks will often have to modified, and it
> can take +20 minutes to resolve some of them.

To say nothing of actually *testing* the patch in each branch, which is
Strongly Recommended if it didn't apply cleanly. I've not infrequently
spent many hours on a difficult back-patch sequence.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pei He 2010-09-22 03:42:15 Compute the number of tuples in a block
Previous Message Tom Lane 2010-09-22 03:31:59 Re: Multi-branch committing in git, revisited