On 19.06.2008, at 10:57, Guillaume Cottenceau wrote:

Andreas Fink <afink 'at' list.fink.org> writes:

On 18.06.2008, at 17:05, Guillaume Cottenceau wrote:

Alexander Malysh <amalysh 'at' kannel.org> writes:

diff --git a/gw/smscconn.c b/gw/smscconn.c
index 21e824d..6654665 100644

Does that mean Alex has some git experience and could positively
examine a request to migrating to git? Kannel still uses CVS, and
it would probably make developers and contributors life easier to
use a more powerful VCS.

Some platforms dont have GIT (like mine).

Is it not unreosonably old? Can you provide details?


I've checked on my network.
the two redhat servers I'm using since a few years, dont have git
all my MacOS X 10.4 and 10.5 servers with latest developer tools dont have git
all my Solaris 8 and 9 machines don't have git.
my ubuntu  server doesnt have git neither.

I'm sure it can be installed from source on all of those machines but its a time consuming task.
I'ts not just apt-get install git

A platform on which no kernel, xorg, wine or ruby on rails
hacking is not possible seems to me a little outdated..?

Do you maybe forget that there are machines with non intel CPU's out there? And especially in telco environment, you see lots of SUN Sparc's. And Kannel is used on those. I don't see why xorg, wine, ruby on rails should be a "dependency" of kannel...


Sometimes, tools a couple of years old may be chosen over very
old tools, even if outdated platforms may need to specifically
install the new tool :)

CVS is old I must admit. My favour would be SVN though.
Things like non deletable directories are really stone age...

Hosting the git repo on the fedora box behind kannel.org should
be pretty easy; there is a lot of documentation out there,
including that one from me if needed (though it's normally aimed
at "shared servers").

The hosting server are not the problem. Users are.
Have you seen GIT for Windows for example?


or for Solaris 8 , HP/UX etc?

For the rest of the Unixes, I suspect compiling git for them
would not be complicated, as git was written in C with a Unix
bias in mind.

... if you have plenty of time.

cvs is there by default often where git is not.

Yes of course. But that argument should be used carefully,
because sometimes better tools which are widely available would
overally benefit to the project.


I currently dont see the benefit of git.
Today I use cvs and svn. Both in exactly the same way. They work fine. So why change to something new?


Also, when moving to git, there's still:

- gitweb allowing any web client to browse the repo

like cvsweb




Reply via email to