From: Junio C Hamano Date: Fri, 11 May 2007 16:45:18 GMT Subject: Re: [FAQ?] Rationale for git's way to manage the index Message-ID: <7v7irfcns1.fsf@assigned-by-dhcp.cox.net> In-Reply-To: <200705111326.35577.jnareb@gmail.com> Jakub Narebski writes: > On Fri, 11 May 2007, Junio C Hamano wrote: >> Jakub Narebski writes: >> >>> In the new version of git I *think* you can use "git add -u path/" >> >> I know you meant well, but next time could you please check the >> fact before speaking? > >> if (i < argc) >> die("-u and explicit paths are incompatible"); > >> The list is getting more and more cluttered recently, perhaps >> which is a good sign that more new people are actually using >> git. Let's try to keep the signal quality of the messages on >> the list high. > > I'm sorry I haven't checked this before writing, especially that > information in the synopsis contradict a bit the information in > the `-u' option description: > ... > -u:: > Update all files that git already knows about. This is what > "git commit -a" does in preparation for making a commit. What does "git commit -a" do? Does it take paths? > I think however that "git add -u dir/" could be quite useful; it is > not needed to have `-u' and explicit paths incompatibile. I tend to agree, and I think that change should not be too difficult. Also it might make sense to have "git commit" use it in the "git-commit --only $paths" codepath. I dunno.