[$] Handling messy pull-request diffstats [$] Handling messy pull-request diffstats

Subsystem maintainers routinely use git request-pull as part of the process of sending work upstream. Normally, the result includes a list of commits included in the request and a nice diffstat that shows which files will be touched and how much of each will be changed; examples abound on the kernel mailing lists. Occasionally, though, a repository with a relatively complicated development history will yield a massive diffstat containing a great deal of unrelated work. The result looks ugly and obscures what the pull request is actually doing. This document describes what is happening and how to fix things up; it is derived from The Wisdom of Linus Torvalds, which has been posted numerous times over the years (example 1, example 2).



from LWN.net https://ift.tt/xKjB7Cq

via IFTTT

Comments

Post a Comment

Popular posts from this blog

Intentional dark pattern by Coinbase or just terrible UI?

Intentional dark pattern by Coinbase or just terrible UI? 2 by jjeaff | 0 comments on Hacker News. I recently needed to check a past transfer to confirm that I was sending some crypto to the same wallet address. In the past, the last few transactions showed up on the "Pay" page. They have since renamed "Pay" to Transfers or something like that. They no longer show past transactions, so I went down a rabbit hole of searching through the app, couldn't find it, then had to google it and found a help page for Coinbase. There is a link in the article to coinbase.com/reports (I can find no way to get to it from the web app except by following the link from the help article.) Once there, you can select the date ranges you want and generate a transaction report in PDF or CSV and then you have to wait a bit while it generates the report for you to download. What kind of UI craziness is this? A user's transaction history is such a basic feature, I can't imagine c...
Read more