+1 to enable this feature. In my view, the use of this feature should be at merger discretion. Squashing can be quite handy to improve clarity and clean up a stream-of-consciousness pull request, but if there are only a couple of commits by different authors or on different topics included in the same PR because one depends on the other, then a standard merge commit might be best for clarity of intent and attribution. Another use-case is when only part of the PR (a subset of commits) is suitable for backport; having separate commits in the original merge allows cherry picking from the public branch not a private feature branch.
Kind regards, Ben. On 30/08/16 19:45, Andrea Aime wrote: > I see no more feedback, > Justin, were your concerns addressed? > Anyone else? > > Cheers > Andrea -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ _______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
