Bo Peng <ben....@gmail.com> writes:
>> Rember the claim put forward a couple of posts ago: "IMHO, we do not
>> have enough manpower to use the git model."
>>
>> Which is just FUD.
>
| Linux/core is huge and there are many components and subcomponents.
| Groups of people work on these subcomponents and submit their tested
| patches to their component maintainer, and eventually to Linus
| himself. The components are more or less *independent* so there are
| little risk of conflict. People working in one component do not need
| to care about *development* of another component. This is where the
| distributed model of git makes sense.
What has linux kernel development to do with lyx and its possible usage
of git?
| LyX is a totally different story. LyX is a much smaller project. If
| two major features are developed separately, there are high
| probability of conflict. Also, due to the manpower issue, it is
| unlikely that two or more people will work on the same feature (share
| a branch). To avoid this problem, a developer tends to submit smaller
| patches (or for each commit) to
>
| 1. avoid conflict.
Very bad reason to commit often. The rule should be to update often
instead and to communicate.
| 2. hope other people can review and test his code.
If you really think that after-commit-review really works, I am afraid
that you are sorely mistaken.
(Why should I bother to redising anything based on a review of code that
works and are already committed? Yes, I have heard that comment on this
list as well...)
| Subversion does this perfectly because everyone is forced to test
| everyone's patch.
If that brings implete/non-working patches on the table nothing is
gained, but a lot of hassle on everyone.
| What git brings to us in this front, other than
| using two commands instead of one?
To you as a developer it brings a lot... and if you fail do get that you
have just not really used git yet.
- git rebase -i
- local commits (which together with get rebase -i makes you place
really nice with a svn repo)
- git stash
(you can do this with subersion as well, but in a lot more
cumbersome way.)
If you feel that your world is shattered because git commit dost not
also push to the subversion repo, then I just do not know what to say.
--
Lgb
