git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Git Mailinglist" <git@vger.kernel.org>
Subject: [GSoC] Git popularity on GSoC
Date: Mon, 21 Jul 2008 22:07:03 +0200	[thread overview]
Message-ID: <bd6139dc0807211307y720bbc07kfb1f2a6db3f25ed0@mail.gmail.com> (raw)

Heya,

There was a poll on the GSoC students mailing list: "What is your
favorite revision control system?". From the 100 responses so far, my
vote topled the balance in favor of Git ;). As a statistics junkie I
think it's fun to see that the only real competition among GSoC
students is Subversion, which has about as much market share as Git.
(Surely the 1 vote for TFS/SourceSafe must have been a misclick.) At
least nobody can claim we're the underdog RCS anymore!

Git		40% (40)
Subversion		39% (39)
Mercurial		7% (7)
CVS		6% (6)
Bazaar 		5% (5)
Perforce		1% (1)
Monotone		1% (1)
Microsoft TFS/SourceSafe		1% (1)
Other		0% (0)
BitKeeper		0% (0)

-- 
Cheers,

Sverre Rabbelier

                 reply	other threads:[~2008-07-21 20:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bd6139dc0807211307y720bbc07kfb1f2a6db3f25ed0@mail.gmail.com \
    --to=alturin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sverre@rabbelier.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).