Hello,
----- Original Message ----
> From: Jakub Narebski <jnareb@xxxxxxxxx>
> To: David Lang <david@xxxxxxx>
> Cc: git@xxxxxxxxxxxxxxx
> Sent: Friday, 12 September, 2008 4:14:58 PM
> Subject: Re: Git User's Survey 2008 partial summary, part 5 - other SCM
>
> On Fri, 12 Sep 2008 00:51, david@xxxxxxx wrote:
> > On Thu, 11 Sep 2008, Jakub Narebski wrote:
> >
> > > A bit suprising for me is high place of Perforce. Another strange
> > > thing (and a bit alarming) is that MS Visual SourceSafe has higher
> > > place than Monotone; but that might be caused by different design and
> > > different target groups of Monotone and Git, which might have caused
> > > that the communities have almost no overlap; people choose either Git
> > > or Monotone, one or the other. BitKeeper has also a very low number
> > > of active users among Git users... but that is not that strange,
> > > considering history.
> >
> > I think you are making the wrong assumption here.
> >
> > Someone may use CVS becouse they contribute to a project that is only
> > availabe via CVS
> >
> > Someone may use Perforce becouse that is the VCS that their company uses
I am in that situation...
> 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.
Since we cannot change management to decide on using git instead of whatever they are using overnight. Best is to have tools like git-p4/git-svn which allows interoperability. Once people gain confidence, they can replace that whatever SCM with git. That is the path I am planning at my place of work.
-dhruva
Get an email ID as yourname@xxxxxxxxx or yourname@xxxxxxxxxxxxxxx Click here http://in.promos.yahoo.com/address
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
