Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Cooksey <thomas.cooksey@trolltech.com>
To: openembedded-devel@openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: Git versus Hg
Date: Wed, 12 Mar 2008 16:35:02 +0100	[thread overview]
Message-ID: <200803121635.02741.thomas.cooksey@trolltech.com> (raw)
In-Reply-To: <20080312172200.47c01671@widy.localdomain>

> > If you choose a well-known SCM system, it's one less 
> > thing new potential developers need to learn. They have enough to 
> > learn as it is.
> > 
> > Cheers,
> > 
> > Tom
> > 
> > PS: Personally, I'd never heard of Hg until reading threads on this
> > list.
> 
> And you won't believe, but many people never heard about Perforce, even
> though it has been alternative (commercial, plus OpenSource loyalty
> program) to CVS for something like decade (cannot be exact, but 7
> years ago it was there for sure). Many large entities still selected
> CVS and spent money on "reduced development productivity and extra
> maintenance costs" (forgive my corporate-speak), just because it was so
> familiar.

Yep, I was one of them. Never heard of perforce before starting at Trolltech. :-)

I think I have limited SCM knowledge. CVS, SVN, Git, Starteam (eeek) were 
the only ones I really knew about, until fairly recently.




  reply	other threads:[~2008-03-12 15:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 23:53 Git versus Hg Philip Balister
2008-03-12  1:56 ` Khem Raj
2008-03-12  7:57 ` Esben Haabendal
2008-03-12  9:16 ` pHilipp Zabel
2008-03-12 13:32   ` Rodrigo Vivi
2008-03-12 14:51   ` Tom Cooksey
2008-03-12 15:22     ` Paul Sokolovsky
2008-03-12 15:35       ` Tom Cooksey [this message]
2008-03-12 14:08 ` Cliff Brake
2008-03-12 14:28   ` Koen Kooi
2008-03-13 14:33     ` Cliff Brake
2008-03-13  8:15   ` Paul Sokolovsky
2008-03-13 11:28     ` Richard Purdie
2008-03-13 19:00       ` Paul Sokolovsky
2008-03-13 20:45         ` Richard Purdie
2008-03-13 14:26     ` Cliff Brake
2008-03-13 15:29       ` Koen Kooi
2008-03-13 15:41       ` Koen Kooi
2008-03-13 20:03         ` Tom Rini
2008-03-13 19:20       ` Paul Sokolovsky
2008-03-13  8:58 ` Koen Kooi
2008-03-13  9:18   ` Paul Sokolovsky
2008-03-13  9:39   ` Esben Haabendal
2008-03-13 10:57   ` Richard Purdie
2008-03-13 11:27   ` pHilipp Zabel
2008-03-13 11:35     ` Marcin Juszkiewicz
2008-03-13 12:17     ` Richard Purdie
2008-03-14 19:44 ` Koen Kooi

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=200803121635.02741.thomas.cooksey@trolltech.com \
    --to=thomas.cooksey@trolltech.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /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