We've recently switched to Git. This thread is meant to give a small insight into the reasons as to why this was done as well as a comment on the problems which arose with the switch.
Q: Why Git?
A: Git has many advantages over Subversion which makes it more comfortable to use for developers. The most important thing is easier branches, i.e. if someone decides to implement a major feature like GLSL support or the texture cache rewrite, you don't need to f*ck up the main development tree but can play around in another branch of the source code without causing problems in the main build.
Q: Where did the revision numbers like r7714 go?
A: Git doesn't use a revision counter, but rather links each changeset with a SHA1 hash. This raised numerous complaints, most of which are either solved easily or which aren't relevant to developers. You need to understand that the whole GoogleCode page is meant to be a developers' place, so there is really no reason for us to care about complaints like "omg I want my rev numbers back!!1".
Q: But how can I tell how old a changeset is just by looking at that hash?
A: You can't. You can, however, simply use your Git tool to show some info about the current commit, which will output the date and branch of the corresponding changeset. Using the CLI of Git, you just need to call "git show <hash>", for example.
Q: Will I still be able to get the Dolphin source with TortoiseSVN?
Q: So, what client should I use to get the source now?
A: You will need another client to get the Dolphin source. For Windows, there's TortoiseGit, GitExtensions as well as msysgit (which is just the command line interface). I'm using TortoiseGit since it's similiar to TortoiseSVN, but GitExtensions is easier to install and might be easier to handle as well. I didn't really try GitExtensions but some devs seem to prefer it, I'd like to hear about which one end users prefer.
For Linux, you most likely already know what you're doing. Just install the CLI of git or use one of the various GUIs available, e.g. gitk or QGit.
Q: How will the homepage handle this now, i.e. how will Git builds be distributed now?
A: We're not entirely sure about that - merely because we haven't heard anything from mamario, yet.
Q: How will the general development process be affected by the switch?
A: (gotta answer this another time)
Q: Why Git?
A: Git has many advantages over Subversion which makes it more comfortable to use for developers. The most important thing is easier branches, i.e. if someone decides to implement a major feature like GLSL support or the texture cache rewrite, you don't need to f*ck up the main development tree but can play around in another branch of the source code without causing problems in the main build.
Q: Where did the revision numbers like r7714 go?
A: Git doesn't use a revision counter, but rather links each changeset with a SHA1 hash. This raised numerous complaints, most of which are either solved easily or which aren't relevant to developers. You need to understand that the whole GoogleCode page is meant to be a developers' place, so there is really no reason for us to care about complaints like "omg I want my rev numbers back!!1".
Q: But how can I tell how old a changeset is just by looking at that hash?
A: You can't. You can, however, simply use your Git tool to show some info about the current commit, which will output the date and branch of the corresponding changeset. Using the CLI of Git, you just need to call "git show <hash>", for example.
Q: Will I still be able to get the Dolphin source with TortoiseSVN?
Q: So, what client should I use to get the source now?
A: You will need another client to get the Dolphin source. For Windows, there's TortoiseGit, GitExtensions as well as msysgit (which is just the command line interface). I'm using TortoiseGit since it's similiar to TortoiseSVN, but GitExtensions is easier to install and might be easier to handle as well. I didn't really try GitExtensions but some devs seem to prefer it, I'd like to hear about which one end users prefer.
For Linux, you most likely already know what you're doing. Just install the CLI of git or use one of the various GUIs available, e.g. gitk or QGit.
Q: How will the homepage handle this now, i.e. how will Git builds be distributed now?
A: We're not entirely sure about that - merely because we haven't heard anything from mamario, yet.
Q: How will the general development process be affected by the switch?
A: (gotta answer this another time)
.
