From: Tim Bird <tim.bird@am.sony.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel <openembedded-devel@openembedded.org>
Subject: Re: Reconsidering the work flow and how the SCM system fits in
Date: Tue, 11 Mar 2008 09:12:21 -0700 [thread overview]
Message-ID: <47D6AF65.1020007@am.sony.com> (raw)
In-Reply-To: <1205243052.4521.82.camel@dax.rpnet.com>
Richard Purdie wrote:
> On Tue, 2008-03-11 at 15:03 +0200, Paul Sokolovsky wrote:
>> It's nice to have that said explicit - different. Supposedly it's more
>> powerful for developers, but how good it is for end users? How many
>> industry entities select git as their in-house SCM? I doubt that too
>> many, knowing too well that many still select just CVS.
> Regarding industrial entities, hopefully we call agree CVS is a pretty
> bad SCM and that proves said industrial entities don't know what they're
> doing, usually since it often it comes down to politics rather than
> technical merit. I know of a few surprising companies using git FWIW
> although I know of a few abominations in use too.
Just a data point...
Sony uses git as its in-house SCM for Linux-related work.
We also use quilt.
> Also, I think more end users coming fresh to OE will know how to do this
> with git in the current climate than with monotone, hg or any other
> distributed SCM.
I would agree with this. monotone is a big reason I'm still
an observer of OE rather than an active participant.
As such, I shouldn't really have a vote. But if I did it would
be for git, purely for personal economy of training.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
next prev parent reply other threads:[~2008-03-11 16:37 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 7:07 Reconsidering the work flow and how the SCM system fits in Holger Freyther
2008-03-11 8:05 ` Koen Kooi
2008-03-11 9:42 ` Holger Freyther
2008-03-11 9:59 ` Koen Kooi
2008-03-11 10:24 ` Richard Purdie
2008-03-11 8:47 ` Esben Haabendal
2008-03-11 9:32 ` Paul Sokolovsky
2008-03-11 9:45 ` Holger Freyther
2008-03-11 10:00 ` Paul Sokolovsky
2008-03-11 10:14 ` Graeme Gregory
2008-03-11 10:38 ` Koen Kooi
2008-03-11 10:56 ` Holger Freyther
2008-03-11 11:21 ` Koen Kooi
2008-03-11 12:25 ` Holger Freyther
2008-03-11 12:38 ` Koen Kooi
2008-03-11 14:23 ` Florian Boor
2008-03-11 12:47 ` John Lee
2008-03-11 14:14 ` Holger Freyther
2008-03-11 16:11 ` Koen Kooi
2008-03-11 9:53 ` Koen Kooi
2008-03-11 13:43 ` Mike (mwester)
2008-03-11 9:41 ` Koen Kooi
2008-03-11 9:52 ` Paul Sokolovsky
2008-03-11 10:04 ` Holger Freyther
2008-03-11 10:25 ` Marcin Juszkiewicz
2008-03-11 10:46 ` Koen Kooi
2008-03-11 11:00 ` Richard Purdie
2008-03-11 12:30 ` Paul Sokolovsky
2008-03-11 12:39 ` Richard Purdie
2008-03-11 13:03 ` Paul Sokolovsky
2008-03-11 13:44 ` Richard Purdie
2008-03-11 14:01 ` Philip Balister
2008-03-11 15:39 ` Paul Sokolovsky
2008-03-11 16:15 ` Richard Purdie
2008-03-11 23:29 ` Paul Sokolovsky
2008-03-11 16:12 ` Tim Bird [this message]
2008-03-11 21:01 ` Rodrigo Vivi
2008-03-11 23:40 ` Paul Sokolovsky
2008-03-12 0:13 ` Richard Purdie
2008-03-11 14:13 ` Florian Boor
2008-03-11 11:49 ` Petr Stetiar
2008-03-11 12:23 ` Paul Sokolovsky
2008-03-11 13:24 ` Florian Boor
2008-03-11 13:39 ` Koen Kooi
2008-03-11 15:49 ` Paul Sokolovsky
2008-03-11 14:12 ` Cliff Brake
2008-03-11 14:57 ` Petr Stetiar
2008-03-11 15:49 ` Richard Purdie
2008-03-11 23:49 ` Paul Sokolovsky
2008-03-12 0:09 ` Richard Purdie
2008-03-12 0:44 ` Paul Sokolovsky
2008-03-12 18:38 ` Leon Woestenberg
2008-03-12 19:00 ` Koen Kooi
2008-03-12 19:09 ` Philip Balister
2008-03-12 20:10 ` Rodrigo Vivi
2008-03-12 20:26 ` Leon Woestenberg
2008-03-12 20:45 ` Koen Kooi
2008-03-12 20:50 ` Stelios Koroneos
2008-03-12 21:34 ` Paul Sokolovsky
2008-03-12 21:54 ` Richard Purdie
2008-03-12 22:54 ` Koen Kooi
2008-03-12 23:24 ` Leon Woestenberg
2008-03-13 0:44 ` Richard Purdie
2008-03-13 8:53 ` Koen Kooi
2008-03-13 11:52 ` Florian Boor
2008-03-13 8:48 ` Marcin Juszkiewicz
2008-03-13 0:18 ` Rod Whitby
2008-03-13 0:59 ` Richard Purdie
2008-03-13 1:22 ` Rod Whitby
2008-03-13 6:33 ` Hans Henry von Tresckow
2008-03-12 21:11 ` Richard Purdie
2008-03-12 21:21 ` Koen Kooi
2008-03-12 21:40 ` Paul Sokolovsky
2008-03-12 22:07 ` Leon Woestenberg
2008-03-12 22:32 ` Paul Sokolovsky
2008-03-13 11:29 ` Marcin Juszkiewicz
2008-05-02 5:30 ` Justin Patrin
2008-03-12 21:49 ` Richard Purdie
2008-03-12 21:37 ` Mikhail Gusarov
2008-03-13 22:29 ` Dmitry Nezhevenko
2008-03-11 13:55 ` Mikhail Gusarov
2008-03-11 10:53 ` Richard Purdie
2008-03-11 11:19 ` Graeme Gregory
2008-03-11 13:17 ` Florian Boor
2008-03-11 12:04 ` Florian Boor
2008-03-11 13:09 ` Mike (mwester)
-- strict thread matches above, loose matches on Subject: below --
2008-03-12 20:34 Mike Westerhof
2008-03-12 20:47 ` Mikhail Gusarov
2008-03-12 20:59 ` Rodrigo Vivi
2008-03-12 21:20 ` Koen Kooi
2008-03-12 21:52 ` Mark Brown
2008-03-12 22:03 Mike Westerhof
2008-03-12 22:21 ` Paul Sokolovsky
2008-05-02 5:46 ` Justin Patrin
2008-03-12 22:48 Mike Westerhof
2008-03-12 23:10 ` Paul Sokolovsky
2008-03-12 23:18 ` Richard Purdie
2008-03-13 0:45 ` Rod Whitby
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=47D6AF65.1020007@am.sony.com \
--to=tim.bird@am.sony.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