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

Re: [RFC] post-commit hook to "fix" patches

From
Stefan Karpinski <stefan.karpinski@gmail.com>
Date
Feb 11, 2009, 09:56 UTC
Message-ID
<d4bc1a2a0902110156nff21282q5fe0a6b7b656a0e6@mail.gmail.com>
In-Reply-To
<d4bc1a2a0902110148u4e13d77cs3dde64d27003e58c@mail.gmail.com>

I'm CC'ing a couple people who replied to the thread I referenced earlier, in case they're interested and would otherwise miss this message.

Especially Marc Weber, who expressed interest in having a good solution to this problem. Does this address what you wanted? I like it because it allows you to transparently and automatically enforce style policy and:

  - it doesn't require modifying git,
  - it's efficient (no overhead except on commit),
  - it doesn't pretend to be a clean/smudge filter (as people pointed
out this isn't reversible),
  - it's portable: everything's written in sh and perl.
Previous: Stefan Karpinski
Message 2 of 2 in “[RFC] post-commit hook to "fix" patches”
  1. Stefan KarpinskiFeb 11, 2009
  2. Stefan KarpinskiFeb 11, 2009

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.