[Releasing] [Development] Change file process & improvement proposal

[Shawn Rutledge]

> On 25 Jan 2017, at 10:21, Edward Welbourne <edward.welbourne at qt.io> wrote:
> 
> I have never heard of these amends <sha1> lines; where are they
> explained ?  In any case, users may find a change interesting even if
> there is no specific earlier commit that can be pinned down as what this
> new change amends - sometimes, the origin of a status quo (being
> amended) is murky, its causes are contentious and most of the lines of
> prior code involved date from the 190MB commit 38be0d1383 that pulled
> most of our code into git in the first place.  Still, maybe your
> amends-spec addresses that …

You’ll find many of them in the logs, and every valid SHA1 (or even unique prefix of a SHA1) turns into a link automatically in some tools such as gitk, and the git log viewer in Creator, which helps a bit with following the chain of reasoning behind a block of code.  Forming a link which identifies a subset of the lines of the patch would be really very cool, but I don’t know of a way.