"Fernando J. Pereda" <[EMAIL PROTECTED]> said: > On Fri, Apr 28, 2006 at 02:49:18PM -0700, Ryan Phillips wrote: > > the only option I saw was git-commit -o and you had to specify the > > files that you wanted to commit. > > > > I tried doing a git-commit paths/ and still everything wants to be > > committed. > > > > It isn't pretty. > > > > Uh, no... thats certainly not true for git-1.3 series, and I belive the > behavior has been consistent since early february this year when the new > commit semantics where introduced. > > See this: > > --- 8< --- > [ $ ~/testy/gitty ] git init-db > defaulting to local storage area > [ $ ~/testy/gitty(master) ] echo something > a > [ $ ~/testy/gitty(master) ] mkdir dir > [ $ ~/testy/gitty(master) ] echo other thing > dir/b > [ $ ~/testy/gitty(master) ] git add . > [ $ ~/testy/gitty(master) ] git commit -m "initial import" > Committing initial tree 6dc01ab7eb7f19983ae76e72ccb63e3e60aa2dc3 > [ $ ~/testy/gitty(master) ] git status > nothing to commit > [ $ ~/testy/gitty(master) ] echo add something here >> dir/b > [ $ ~/testy/gitty(master) ] echo something there >> a > [ $ ~/testy/gitty(master) ] git status > # > # Changed but not updated: > # (use git-update-index to mark for commit) > # > # modified: a > # modified: dir/b > # > nothing to commit > [ $ ~/testy/gitty(master) ] git commit -m "Only things in dir/?" dir/ > [ $ ~/testy/gitty(master) ] git status > # > # Changed but not updated: > # (use git-update-index to mark for commit) > # > # modified: a > # > nothing to commit > [ $ ~/testy/gitty(master) ] > --- 8< --- > > It is the same even if you did 'git update-index a' before 'git commit > -m ... dir/'. However that's something you won't do unless you know what > you're doing :) >
I'm testing with 1.3.1. You are correct. The text the is printed by git is a bit confusing. If the portage tree can scale to it, then I'm for it. Thanks for the clarification. -ryan
pgpUxk2oFOLaj.pgp
Description: PGP signature
