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

Re: Automatically exclude hunks from the commit

From
Wincent Colaiuta <win@wincent.com>
Date
Jul 20, 2010, 05:36 UTC
Message-ID
<51F8E66E-9CDD-466A-8411-38CA8431D8AC@wincent.com>
In-Reply-To
<4C4511C8.8090405@workspacewhiz.com>
El 20/07/2010, a las 05:02, Joshua Jensen escribió:
> I have some files I update frequently where I have some normally commented out debug code purposely uncommented during development.  Git's hunk-level staging saves the day.  I can stage everything but the debug code without issue.
> 
> This got me to thinking.  Is there a better way?  Is there a facility in Git where I could mark a hunk as 'permanently frozen unstaged'?  Anything marked as such would never be staged for commit.  I could rest assured I would never accidentally commit my debug code, be it extra printfs or a development server or a password or so on.
A custom pre-commit hook might be of some use here. You could create one which rejects changes which are obviously debug code.

Cheers, Wincent

Previous: Joshua JuranNext: Michael J Gruber
Message 3 of 4 in “Automatically exclude hunks from the commit”
  1. Joshua JensenJul 20, 2010
  2. Joshua JuranJul 20, 2010
  3. Wincent ColaiutaJul 20, 2010
  4. Michael J GruberJul 20, 2010

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.