Excerpts from Andrew Dunstan's message of mié jul 21 15:11:41 -0400 2010: > > Jonathan Corbet wrote:
> > That seems like a terrible idea to me - why would you destroy history? > > Obviously I've missed a discussion here. But, the first time somebody > > wants to use bisect to pinpoint a regression-causing patch, you'll wish you > > had that information there. > > So when a committer pushes a patch it should add one fast-forward commit > to the tree. We want to be able to bisect between these commit objects, > but not between all the work product commits that led up to them. Of > course, developers, committers and testers can keep what they like > privately - we're only talking about what should go in the authoritative > repo. I don't disagree that we're going to squash commits, but I don't believe that developers will be able to keep "what they like privately". The commit objects for the final patch are going to differ, if only because they have different parents than the ones on the main branch. Of course, they will be able to have a local branch with their local patch, but to Git there will be no relationship between this branch and the final, squashed patch in the authoritative repo. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
