<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi Larry,</div><div><br></div><div><div><div>On 13 Dec 2016, at 05:20 , Lawrence Velázquez <<a href="mailto:larryv@macports.org">larryv@macports.org</a>> wrote:</div><blockquote type="cite"><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Please clean up the commit message when you perform squash merges. Most of the text here is outdated Git metadata (old SHA-1 hashes, repeated author name, irrelevant authorship dates).</div></blockquote></div><div><br></div><div><div>yes, you’re right, I should have stripped that down...</div><div><br></div><div><br></div><div>Yet, the git metadata is - also to my surprise - still valid, which can be verified by clicking all the links on the commit’s page:</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/macports/macports-ports/commit/47c0c4f682b22803ae250258187544187d50f898">https://github.com/macports/macports-ports/commit/47c0c4f682b22803ae250258187544187d50f898</a></div><div><br></div><div>That will produce the 4 separate commits just fine.</div><div><br></div><div>Interesting.</div><div><br></div><div>Greets,</div><div>Marko</div></div></div></body></html>