C167 wrote:divVerent wrote:Anyway... another reason NOT to use git and hg is that they are weird tools that don't come preinstalled with distros, and thus are weird niche tools most people don't have and know how to use.
So, you think svn is preinstalled? how do you think that it is? I _never_ had a debian version (at least since sarge) that came with svn fresh from installation. _never_
No, I just claim that people are very likely to already have svn installed, but not to have git installed. git is too new and weird for that.
divVerent wrote:According to Debian Popcon:
31% of users have subversion
26% of users have cvs
10% of users have git-core
4% of users have mercurial (hg)
2% of users have darcs
1% of users have tla (GNU arch)
According to Ubuntu Popcon:
16% of users have subversion
12% of users have cvs
4% of users have git-core
2% of users have mercurial
0.4% of users have tla (GNU Arch)
0.3% of users have darcs
Okay, here you have the numbers that tell you that x percent of $distro users that take part in popcon have VCS Y installed on their system. it does _not_ tell you, that the tools are part of the installation.
I did not claim that. Actually, the numbers show that they are NOT part of the installation. But they give a general idea about the popularity of the tools, and the probability that people have them already. And many already HAVE svn installed.
divVerent wrote:Also think of users e.g. in computer pools who don't have root access there. They can't just "simply" install git, while it's very likely that they have svn preinstalled.
From my point of view, the computer pools in karlsruhe (germany) have both, git and svn preinstalled.
And please tell me how many people that follow the nexuiz and dp repositories do that from some computer pools? and even if, just carry the tools on a usb stick, its not that hard and well known practice when having to work on a different computer without admin permissions.[/quote]
On Linux, binaries compiled on one distro typically don't work on another one.
divVerent wrote:And Mercurial, darcs, arch are RIGHT out.
Cause they are not preinstalled? Cause they don't use simple revision numbers?
No, but because they are even less popular than git. With these tools, we'd have a GUARANTEE that every user has to install them and learn about them ONLY for Nexuiz. Almost nobody has them installed at the moment.
Yea the github interface may suck in your eyes, but do not blame the other free systems.
I was referring to github because people were suggesting moving development over to that.
To come to popilarity of VCS', like [-z-] pointed out, git is quite young and did not have the time to become better and more popular like svn had.
And exactly that is a reason not to use it yet. It should first be used in more "low level" projects which require more programming background, e.g. Linux (already using it).
i had two scripts in a project that relyed on svn, and when changing to git, i could change them within some minutes.
So? I don't care. I refuse to change VCS "just because we can". Until now, no single reason was presented why we would GAIN from git (as all the advantages of git that were ever presented here also apply if using git-svn), but many reasons were presented why we would LOSE by using it.
Next point: commits like 6682 or 6165 simply do not happen, cause git forces you to enter at least a short comment.
So does svn. So? That was not the point.
The point was that short increasing numbers are very convenient for seeing whether someone has a change or not. Also, look at the bottom right corner of the darkplaces console. It shows:
darkplaces-nexuiz linux 18:28:03 mar 21 2009 8981:8982M release
The last number there is:
- the svn revision, if unchanged
- the range of svn revisions, if a selective "update" was done
- a "M" is appended if there are local changes
How does a git-hash tell you whether any previous change is in it? The compile date does not help there. Even if we would show the date of the most recent commit, it would not help, as it does not show if all previous commits were applied or not. The thing is, svn DOES show that.
Well, if you could provide a script that outputs a "short revision number" for git, maybe in the format:
YYYYMMDDNNN
where NNN is an increasing number of the commits of today.
The letter "M" is to be appended if it is locally modifed, or if not ALL commits before the most recently applied one are applied.
If you could do that, and also make a web frontend supporting such "revision numbers", we could use that and replace svnversion by it.
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again
You can vary the number of "MS", so you can clearly see it's MS which is causing it.