Author Topic: Development announcement: Movement to Git  (Read 3634 times)

Yggdrasil

  • Local Moderator
  • Ornithopter
  • ********
  • Posts: 408
    • View Profile
Development announcement: Movement to Git
« on: 8 January 2011, 12:56:14 »
We switched our version control system from subversion to git. So, all early testers which are currently using subversion to get the latest code, please switch to our new git repository.

See the compile guide for instructions:
http://sourceforge.net/apps/trac/glestae/wiki/CompileGuide
(Mac will be updated very soon)

If you're unfamiliar with git, this might be a nice guide:
http://git-scm.com/course/svn.html

Edit By Omega: Renamed topic for more specific title
« Last Edit: 19 January 2011, 03:13:42 by hailstone »

Conzar

  • Guest
Re: Development announcement
« Reply #1 on: 8 January 2011, 13:52:46 »
Awesome!!!!  GIS is also using git ... maybe all of the glest community can be unified eventually with git?

will

  • Golem
  • ******
  • Posts: 783
    • View Profile
Re: Development announcement
« Reply #2 on: 8 January 2011, 14:51:02 »
This is very good news

ultifd

  • Airship
  • ********
  • Posts: 4,443
  • The Glest Video Guy :) The one and only. :P
    • View Profile
    • My Youtube Channel
Re: Development announcement: Movement to Git
« Reply #3 on: 17 January 2011, 19:12:23 »
Don't forgot to update the windows guide!  :)

hailstone

  • Local Moderator
  • Battle Machine
  • ********
  • Posts: 1,568
    • View Profile
Re: Development announcement: Movement to Git
« Reply #4 on: 19 January 2011, 03:18:34 »
I've updated the Windows Guide. I haven't actually tried with Tortoise Git since I use Git Extensions (see the other guide) but it should work.
Glest Advanced Engine - Admin/Programmer
https://sourceforge.net/projects/glestae/

kris9700

  • Guest
Re: Development announcement: Movement to Git
« Reply #5 on: 2 April 2011, 23:17:56 »
Great news!

hailstone

  • Local Moderator
  • Battle Machine
  • ********
  • Posts: 1,568
    • View Profile
Re: Development announcement: Movement to Git
« Reply #6 on: 1 May 2011, 06:35:36 »
git describe might be an ok way to reference an untagged commit.

Code: [Select]
0.3-640-g475cfcfThe first is the tag, then number of commits in addition to the tag commit, abbreviated object name for the commit.
Glest Advanced Engine - Admin/Programmer
https://sourceforge.net/projects/glestae/

 

anything