From: david@lang.hm
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git User's Survey 2008 partial summary, part 5 - other SCM
Date: Sat, 13 Sep 2008 14:11:29 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0809131408010.17867@asgard.lang.hm> (raw)
In-Reply-To: <200809121244.59067.jnareb@gmail.com>
On Fri, 12 Sep 2008, Jakub Narebski wrote:
> On Fri, 12 Sep 2008 00:51, david@lang.hm wrote:
>> On Thu, 11 Sep 2008, Jakub Narebski wrote:
>>
> True, I have forgot that "I use this SCM" (or "I used this SCM") doesn't
> necessarily mean that one _choose_ this SCM. One can use some SCM
> because it is SCM project uses, or because their company requires it;
> but not necessary, as git-svn and git-p4 show one can use Git, and
> make it interact with respectively Subversion and Perforce, and trying
> to make it look like one uses this other SCM.
I would expect people to still count those as using the other SCM. git-svn
and git-p4 can do a lot, but they don't do everything, once in a while I
would expect to need to use the native commands for the upstream SCM
>> I find it interesting that the number of people who use git and the other
>> DVCS systems in so small. Is this becouse the 'market share' of those
>> other systems is small? Or becouse people who learn git aren't willing to
>> put up with other systems (or vice-versa)? Or is there some other trend
>> or tendancy that makes people who select one DVCS more likely to work on
>> similar projects, so people interested in those types of projects will
>> generally just see a single DVCS system
>
> I don't think 59% (in the example case of using currently Subversion)
> is small. Take into account for example that there are people who (as
> seen from responses to other questions in this survey) use SCM (Git)
> only to track their private work, never publishing. Then there are
> people who do not track (perhaps with exception of web interfaces)
> other projects development using version control systems, even if they
> do follow their development.
Subversion is not a Distributed SCM. I am pointing out the much smaller
overlap between distributed SCM systems.
David Lang
next prev parent reply other threads:[~2008-09-13 21:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 14:07 Git User's Survey 2008 partial summary Jakub Narebski
2008-09-03 14:45 ` Shawn O. Pearce
2008-09-03 15:20 ` H.Merijn Brand
2008-09-03 16:25 ` Felipe Contreras
2008-09-04 2:43 ` David Aguilar
2008-09-05 22:17 ` Jan Hudec
2008-09-06 4:17 ` David Aguilar
2008-09-03 15:00 ` David Brown
2008-09-03 15:41 ` Scott Chacon
2008-09-03 16:00 ` Jakub Narebski
2008-09-04 13:23 ` Git User's Survey 2008 partial summary, part 2 Jakub Narebski
2008-09-06 2:22 ` Git User's Survey 2008 partial summary, part 3 Jakub Narebski
2008-09-06 5:15 ` Shawn O. Pearce
2008-09-06 8:27 ` Andreas Ericsson
2008-09-07 23:07 ` Jonas Fonseca
2008-09-07 23:47 ` Shawn O. Pearce
2008-09-06 22:17 ` Git User's Survey 2008 partial summary, part 4 - how do we use Git Jakub Narebski
2008-09-07 8:31 ` Andreas Ericsson
2008-09-07 8:44 ` Jakub Narebski
2008-09-11 20:14 ` Git User's Survey 2008 partial summary, part 5 - other SCM Jakub Narebski
2008-09-11 21:03 ` Anatol Pomozov
[not found] ` <48C98F92.40903@workspacewhiz.com>
2008-09-11 22:05 ` Jakub Narebski
2008-09-11 21:54 ` Jeff King
2008-09-11 22:51 ` david
2008-09-12 10:44 ` Jakub Narebski
2008-09-13 21:11 ` david [this message]
2008-09-13 22:03 ` Jakub Narebski
2008-09-15 11:51 ` Mark Brown
2008-09-14 10:45 ` Nguyen Thai Ngoc Duy
2008-09-14 13:32 ` Jakub Narebski
2008-09-15 3:39 ` david
2008-09-15 7:00 ` Andreas Ericsson
2008-09-16 17:12 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2008-09-12 11:11 dhruva
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=alpine.DEB.1.10.0809131408010.17867@asgard.lang.hm \
--to=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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).