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

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. 		 	   		  
_________________________________________________________________
Browse profiles for FREE! Meet local singles online.
http://clk.atdmt.com/NMN/go/150855801/direct/01/

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

quoted

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/

Hi

On Wed, Mar 24, 2010 at 1:47 AM, Dario Bertini [off-list ref] wrote:

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 )

check out the pre-commit hook:

  http://www.kernel.org/pub/software/scm/git/docs/githooks.html#_pre_commit

You could make it scan the directory, then veto the execution of
git-commit if any untracked files are found.

-- 
Cheers,
Ray Chuan