Best practices for merging?

[Brandon Allbery]

On Tue, Feb 2, 2016 at 9:23 AM, Alexander Berntsen <alexander at plaimi.net>
wrote:

> On 02/02/16 15:20, Brandon Allbery wrote:
> > Only if it builds and passes tests across all ten commits.
> Yes, obviously. I have never worked anywhere where breaking commits
> were allowed, and I did not intend to suggest that breaking commits
> were a Good Idea or useful. They emphatically aren't.
>

The point is, this only applies once it's in the ghc repo. Works in
progress may well have such commits as long as they are cleaned up on
pushing --- which is why you would squash commits together losing
intermediate history, which is what started this thread. (This point was
actually made earlier in the thread, just not in so many words.)

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20160202/90d0ac17/attachment-0001.html>