[crossfire] Crossfire should use Git

[Steven Johnson]

I'm not a regular contributor either but I believe mercurial (hg) is the
better choice as well. Plus the site Bloody Shade mentioned
http://hginit.com/ easily explains the transition from svn to hg.
On Jun 13, 2014 9:29 AM, "Bloody Shade" <bloodyshade at gmail.com> wrote:

> I'm not sure I can agree with a move to Git, personally.
>
> There's plenty of drawbacks that also come with git (not that other
> version controls don't).
> I personally use mercurial (hg) for my projects and you can find more info
> on it and see if you like it at: http://hginit.com/
>
> I found this article with some things I also don't like about git, in case
> anybody else is wondering (although I'm sure there's more):
> http://steveko.wordpress.com/2012/02/24/10-things-i-hate-about-git/
>
> Then again, I'm not a regular contributor, so feel free to ignore this,
> but I thought it would be worth throwing my 2 cents.
>
> On 6/13/2014 10:13 AM, Kevin Zheng wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi all,
>>
>> Crossfire originally lived in the world of CVS, until a handful of brave
>> knights ventured to move it to SVN. Today I believe it is time to move
>> again, and this time to Git.
>>
>> Git is a distributed version control system, which means that checking
>> out an old revision or reading the commit log does not require accessing
>> the sometimes painfully slow servers on the Internet. Each 'clone' of
>> the repository is a fully-functioning repository on its own. This means
>> that developers, even those who do not have commit access, can work on
>> projects at their own pace and submit them with tools such as `git
>> format-patch` and others.
>>
>> Git makes branching easy. It makes maintaining them manageable. As an
>> example, several important fixes were made in 'trunk', which have yet to
>> be backported to 1.12.0. In addition, there are no release engineering
>> branches, which means that each release is simply cut from the next
>> 'trunk' state in line. Even "trivial" fixes could benefit from topic
>> branches, but SVN does not make this easy, convenient, or fun. Using Git
>> branches would help create a more stable codebase by improving release
>> engineering and adopting intermediate "stable" branches that servers can
>> track. A recent autotools bug that wiped server configuration files, for
>> example, could have been prevented if changes on the bleeding edge were
>> evaluated by test servers first.
>>
>> Git is not terribly difficult to use. Right now I access the SVN
>> repository through a local Git clone, but this is inadequate because I
>> cannot publish my topic branches (without considerably difficulty). A
>> migration that preserves tags, branches, and full revision history can
>> be made as fast as the revisions are pulled from SVN.
>>
>> In summary, a few important benefits of using Git:
>>
>> - - Contributors can work on the code easier, with revision control.
>> - - Distributed, so works without (slow) Internet access.
>> - - Encourages branching -> more stable codebase.
>> - - Easy to use and migrate to.
>> - - Full (all revision history) repository size: 21.7 MiB (server), 13.9
>>    MiB (client), 106.1 MiB (maps)
>>
>> However, there are a few immediate problems:
>>
>> Most projects using SVN make extensive use of the revision number
>> identifiers. Crossfire is no different. Git has revision (commit)
>> identifiers, but they are meaningless without the repository, whereas
>> SVN increments the number for each commit. I do not believe this is an
>> issue, because client compatibility is not determined by this
>> specifier, plugin versions are only checked to match, and other uses
>> of the identifier can be removed.
>>
>> Of course, comments, questions, and hate mail are always welcome.
>>
>> Thanks,
>> Kevin Zheng
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>
>> iQEcBAEBAgAGBQJTmvjyAAoJEOrPD3bCLhCQsEIH/2CnCPs/FmKlGmgkMw98zo/b
>> vIFMiFiMZsuEteKUajXZb3+OfabyvCTBJZc3nVOlVwxt6xT+9NcspmdPYIofqt2M
>> 24fhSY7LqSF5Odc/afQX6JrA21fgF/ryU6jc1Iri2+13Wk6TDEhQqZ/ASdSmaaZm
>> IXd9iPb8D7EbSmp0pqvAGKriExVZDSIuukXmOQzbjG8mqFgczBnNdxP62bPh2H03
>> NyMbd+nCFfaaXAca/5wGZgrqmx0OU8DiRx9FTKzwp1/Ku3t09PT9aUbuOY6qUKAU
>> kdOQfdp8naAxCbf38B/9k+IU5lk+JFcbs576X3lreU0xyr1byZyparkfNOLk3XE=
>> =lsHS
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> crossfire mailing list
>> crossfire at metalforge.org
>> http://mailman.metalforge.org/mailman/listinfo/crossfire
>>
>>
>
> ---
> This email is free from viruses and malware because avast! Antivirus
> protection is active.
> http://www.avast.com
>
> _______________________________________________
> crossfire mailing list
> crossfire at metalforge.org
> http://mailman.metalforge.org/mailman/listinfo/crossfire
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.metalforge.org/pipermail/crossfire/attachments/20140613/c36ec7ea/attachment.html>