1 |
"Fernando J. Pereda" <ferdy@g.o> said: |
2 |
> On Fri, Apr 28, 2006 at 02:49:18PM -0700, Ryan Phillips wrote: |
3 |
> > the only option I saw was git-commit -o and you had to specify the |
4 |
> > files that you wanted to commit. |
5 |
> > |
6 |
> > I tried doing a git-commit paths/ and still everything wants to be |
7 |
> > committed. |
8 |
> > |
9 |
> > It isn't pretty. |
10 |
> > |
11 |
> |
12 |
> Uh, no... thats certainly not true for git-1.3 series, and I belive the |
13 |
> behavior has been consistent since early february this year when the new |
14 |
> commit semantics where introduced. |
15 |
> |
16 |
> See this: |
17 |
> |
18 |
> --- 8< --- |
19 |
> [ $ ~/testy/gitty ] git init-db |
20 |
> defaulting to local storage area |
21 |
> [ $ ~/testy/gitty(master) ] echo something > a |
22 |
> [ $ ~/testy/gitty(master) ] mkdir dir |
23 |
> [ $ ~/testy/gitty(master) ] echo other thing > dir/b |
24 |
> [ $ ~/testy/gitty(master) ] git add . |
25 |
> [ $ ~/testy/gitty(master) ] git commit -m "initial import" |
26 |
> Committing initial tree 6dc01ab7eb7f19983ae76e72ccb63e3e60aa2dc3 |
27 |
> [ $ ~/testy/gitty(master) ] git status |
28 |
> nothing to commit |
29 |
> [ $ ~/testy/gitty(master) ] echo add something here >> dir/b |
30 |
> [ $ ~/testy/gitty(master) ] echo something there >> a |
31 |
> [ $ ~/testy/gitty(master) ] git status |
32 |
> # |
33 |
> # Changed but not updated: |
34 |
> # (use git-update-index to mark for commit) |
35 |
> # |
36 |
> # modified: a |
37 |
> # modified: dir/b |
38 |
> # |
39 |
> nothing to commit |
40 |
> [ $ ~/testy/gitty(master) ] git commit -m "Only things in dir/?" dir/ |
41 |
> [ $ ~/testy/gitty(master) ] git status |
42 |
> # |
43 |
> # Changed but not updated: |
44 |
> # (use git-update-index to mark for commit) |
45 |
> # |
46 |
> # modified: a |
47 |
> # |
48 |
> nothing to commit |
49 |
> [ $ ~/testy/gitty(master) ] |
50 |
> --- 8< --- |
51 |
> |
52 |
> It is the same even if you did 'git update-index a' before 'git commit |
53 |
> -m ... dir/'. However that's something you won't do unless you know what |
54 |
> you're doing :) |
55 |
> |
56 |
|
57 |
I'm testing with 1.3.1. You are correct. The text the is printed by |
58 |
git is a bit confusing. If the portage tree can scale to it, then I'm |
59 |
for it. |
60 |
|
61 |
Thanks for the clarification. |
62 |
|
63 |
-ryan |