git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git Diff feature request

From
NGNick Gearls <nickgearls@gmail.com>
Date
Jan 3, 2022, 07:53 UTC
Message-ID
<e3e2cf38-31e0-7b3e-af79-88226dcdabe5@gmail.com>
In-Reply-To
<CA+JQ7M_tQG4yzSeHjZxPWuWEOM=iSLrWxojQGcpL9E7FcoXLRg@mail.gmail.com>

When you want to compare 2 versions of a repo you don't own, you don't have the option to apply a formatting standard ...

On 31-12-2021 12:15, Erik Cervin Edin wrote:
Show 5 quoted lines
> On Fri, Dec 31, 2021 at 11:23 AM<rsbecker@nexbridge.com>  wrote:
>> One interesting technique I have seen used is to set up a pre-commit hook and/or clean filter to format code according to corporate/team standards. Reprocessing code prior to the commit would allow a normalization of coding standards and removing of EOL or space/tab concerns.
>> ...
>> We use a similar technique (enforced only by policy right now, not a hook), which is to require code to run through standard IDE source formatting. Improperly formatted code hitting pull requests gets a decline until the code is properly formatted.
> I agree with Randall, the easiest solution is to adhere to a formatting standard
Previous: Erik Cervin EdinNext: Erik Cervin Edin
Message 4 of 5 in “Git Diff feature request”
  1. Nick GearlsDec 30, 2021
  2. rsbecker@nexbridge.comDec 30, 2021
  3. Erik Cervin EdinDec 31, 2021
  4. Nick GearlsJan 3, 2022
  5. Erik Cervin EdinJan 3, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.