1 |
Ryan: |
2 |
|
3 |
I think you are talking about very old versions of Git: |
4 |
|
5 |
On Fri, Apr 28, 2006 at 02:20:43PM -0700, Ryan Phillips wrote: |
6 |
> What I meant is, if you have a change within one directory pending |
7 |
> a commit, and you have a commit pending in a current directory, both |
8 |
> files will be picked up for the commit. I think that is bad. That |
9 |
> means you can't have pending changes not ready for commit and commit |
10 |
> something. |
11 |
|
12 |
Of course you can have pending commits. You can even have uncommited |
13 |
changes in your index since git-commit uses a temporary index when doing |
14 |
this kind of checkins. |
15 |
|
16 |
> yes. git-commit will allow the commit, it will walk the directories |
17 |
> backwards, but it will find all the pending changes and want to commit |
18 |
> them. |
19 |
|
20 |
It will if you don't use git-commit correctly :) |
21 |
|
22 |
> I don't think that is beneficial. I'm open to comments though. |
23 |
|
24 |
'git commit' semantics are a bit different from 'cvs commit' and 'svn |
25 |
commit' semantics. That's probably the reason you faced that problem :) |
26 |
|
27 |
Cheers, |
28 |
ferdy |
29 |
|
30 |
-- |
31 |
Fernando J. Pereda GarcimartÃn |
32 |
Gentoo Developer (Alpha,net-mail,mutt,git) |
33 |
20BB BDC3 761A 4781 E6ED ED0B 0A48 5B0C 60BD 28D4 |