Tomahawk, KDE, and other stuff
KDE Git: Three servers, better commit URLs
Two quick updates on Git stuff:
First, we now have three anongit servers in rotation. We could probably make do with 0.25 of a single anongit server at the current load, but that will change quickly once kdelibs and co switch over from SVN, so it’s good to be ready.
Second, the generated commit URLs will always be given with the full commit hash, but the commit resolver now supports using partial hashes in case you want to shorten it yourself. For instance, you could manually change the commit URL http://commits.kde.org/amarok/cf17de39f9021064a713db965487be6e3d75a186 to http://commits.kde.org/amarok/cf17de39 to give out a shorter URL.
That’s all; if you were in the States I hope you had a good Thanksgiving. 
RSS
email
Print
PDF
Add to favorites
Identi.ca
Twitter
Google Buzz
Facebook
del.icio.us
Google Bookmarks
Reddit
Technorati
Slashdot
Digg
Thanks for all of your hard work, it is great to see the move to git progressing forward. The new project sites look really good too.
Just out of curiousity – how do you sync those 3 servers when they all are available for write access to the repositories?
Do they use a common blockdevice (DRDB) or filesystem (some cluster FS)?
Are there any git internal mechanisms to do this?
Regards,
Elias P.
Hmm, maybe I should actually read what you wrote….
3 ‘anongit’ servers, so there’s only read access which is far easier to do than servers where write access is provided.
Yep — only for read access. Syncing is done via a push mechanism from git.kde.org (rather than a pull mechanism; this allows for disabling updates centrally if they need to be tested, and making sure updates happen on the servers in a predictable order). The scripts are open-source; you can see them at https://projects.kde.org/projects/repo-management