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

RE: commit --strict feature request

From
TMTim Mazid <timmazid@hotmail.com>
Date
Mar 24, 2010, 01:14 UTC
Message-ID
<SNT124-W65458CD48BBB9A6A831FDEC4250@phx.gbl>
In-Reply-To
<SNT124-W659C1D09B747F338E04DF4C4250@phx.gbl>
Show 43 quoted lines
> From: timmazid@hotmail.com
> To: berdario@gmail.com; git@vger.kernel.org
> Subject: RE: commit --strict feature request
> Date: Wed, 24 Mar 2010 12:10:06 +1100
>
>
>> Date: Tue, 23 Mar 2010 18:47:16 +0100
>> From: berdario@gmail.com
>> To: git@vger.kernel.org
>> Subject: commit --strict feature request
>>
>> Hi, i usually use bzr, and today i was searching for a commit --strict
>> equivalent in git... i asked around and it seems there isn't one, so i'm
>> writing this.
>>
>> basically, by doing commit --strict it refuses to commit if there are
>> untracked (and thus not ignored) files in the tree, this helps against
>> forgetting to add new files (actually i find it so useful that i've even
>> changed commit to be an alias to commit --strict in my bzr aliases )
>>
>>
>> greetings
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
> Hi,
>
> I think (someone correct me if I'm wrong) that being able to commit only part of the changes you made at a time is one of the major points of git (at least for me, anyway), so such a feature might go against the whole design.
>
> Also, what you could use is 'git commit -v', which allows you to review all the changes you are commiting, and allows you to write a better commit message anyway, as you can look at the changes, instead of going from memory.
>
> Another option might be to use a gui, such as 'git gui', which gives you a clear visual of what files have unstaged changes.
>
> Hope that helps until somebody competent replies.
>
> Tim.
>
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
 
Oh, and I just realised, 'git commit' does actually show you a 'git status' (by default in v1.7.0) when you write your message anyway, so you don't even need the '-v' to see what files are staged/unstaged. 		 	   		  
_________________________________________________________________
Browse profiles for FREE! Meet local singles online.
http://clk.atdmt.com/NMN/go/150855801/direct/01/
Previous: Tim MazidNext: Tay Ray Chuan
Message 3 of 4 in “commit --strict feature request”
  1. Dario BertiniMar 23, 2010
  2. Tim MazidMar 24, 2010
  3. Tim MazidMar 24, 2010
  4. Tay Ray ChuanMar 27, 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.