1 |
On Wed, Jan 17, 2007 at 09:03:59AM +0100, Markus Ullmann wrote: |
2 |
> >1. Git currently requires you to check out the whole repository. |
3 |
> > This includes *all of the history*. |
4 |
> >2. Git cannot update portions of the repository, it can only update |
5 |
> > the entire thing. |
6 |
> |
7 |
> This was one of the big reasons. They (and we maybe as well) have people |
8 |
> there with 56k/64k dialup connections. Checking out the whole thing |
9 |
> would take ages. |
10 |
See lower down in the GLEP where it states that upstream are working on |
11 |
it, and such features would be completed sooner is Gentoo added some |
12 |
manpower. I do however personally expect them to be ready by mid-2007 |
13 |
already. |
14 |
|
15 |
> Second thing was that absolutely none of the scripts would be able to |
16 |
> handle it and they would have to be rewritten from ground up whereas |
17 |
> most of them would work with svn if you just change the binary path (or |
18 |
> symlink it even) |
19 |
I disagree with this statement. There are several mapping scripts that |
20 |
provide interfaces for the old CVS commands as close as possible |
21 |
(exceedingly close actually). |
22 |
|
23 |
> > The conversion to GIT from CVS was also lengthy |
24 |
> > (approximately two weeks) althought many projects attempted a switch |
25 |
> > this summer and tools have improved in speed. |
26 |
> This one was the third. At the time they tried, the conversion could not |
27 |
> be suspended, so cvs would have to be taken offline for a really long time. |
28 |
Upstream has moved beyond this point. If we were to convert to GIT right |
29 |
now, it is intelligent enough to be able to start the conversion with a |
30 |
snapshot, and then add the changes between the snapshot being taken, and |
31 |
the final point after the initial conversion is complete. |
32 |
|
33 |
> And the last thing was the idea about distribution. There is one |
34 |
> "centrally" maintained tree and people commit to it all day. So the |
35 |
> chance of getting conflicts in pushes if one is on tour for three days |
36 |
> would be very likely and so the distributed part of the VCs wouldn't be |
37 |
> helpful. |
38 |
I refute this statement. You are no more or less likely to get conflicts |
39 |
than with CVS (ignoring that fact that GIT has smarter merge |
40 |
algorithms). If you do a CVS checkout, go away for 3 days, and then try |
41 |
to commit, CVS will require you to update and resolve checkouts before |
42 |
accepting your commit. GIT is no different, except that you can at least |
43 |
have multiple revisions of your changes locally while working on them. |
44 |
|
45 |
-- |
46 |
Robin Hugh Johnson |
47 |
Gentoo Linux Developer |
48 |
E-Mail : robbat2@g.o |
49 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |