From: Junio C Hamano Date: Tue, 14 Jun 2005 05:52:25 GMT Subject: Re: [PATCH] Adding Correct Useage Notification and -h Help flag Message-ID: <7vaclt8oyu.fsf@assigned-by-dhcp.cox.net> In-Reply-To: <1118726714.8712.22.camel@localhost.localdomain> >>>>> "JP" == James Purser writes: JP> When running git commit I am told to run git-update-cache JP> against the files I want to commit. Would it be easier to JP> have the git-commit-script run this itself? Take out that JP> second step and all that. That's a question better asked Linus, not me. My preference would be (1) to ask the user if he wants us to automatically run git-update-cache to all of those files, giving him an option to decline and sort things out himself; or (2) leave things as they are. The core GIT treats the index file and the working directory contents two logically separate entities, and we always require the user to consciously tell us what to put in and remove from the index file. The core GIT is all about committed tree objects and the index file, and the working directory is merely a temporary area the user can use to build the state the user wishes to have in the index file. From this point of view, running git-update-cache ourselves without asking the user is a definite no-no.