Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Cliff Brake <cliff.brake@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Reflection on MTN to GIT change?
Date: Mon, 20 Apr 2009 19:42:02 -0400	[thread overview]
Message-ID: <f96d234e0904201642o7144b20dr18a3ac4308cab3bb@mail.gmail.com> (raw)
In-Reply-To: <c384c5ea0904201542y7d6de263ve1de19745ed29d47@mail.gmail.com>

On Mon, Apr 20, 2009 at 6:42 PM, Leon Woestenberg
<leon.woestenberg@gmail.com> wrote:
> Hello,
>
> just wanted to see how we feel about the move to git as our scm?
>
> Personally, I like the speed of git, I like the very healthy commit
> rate we have in OE now*. Still struggling with the concept of git
> though.
> Overall, a good move I think.

It has been a positive change from my perspective.  About everything I
do is less pain, and supporting customers using OE is easier.

Cliff

-- 
=======================
Cliff Brake
http://bec-systems.com



  reply	other threads:[~2009-04-20 23:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 22:42 Reflection on MTN to GIT change? Leon Woestenberg
2009-04-20 23:42 ` Cliff Brake [this message]
2009-04-21 11:44 ` Michael 'Mickey' Lauer

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=f96d234e0904201642o7144b20dr18a3ac4308cab3bb@mail.gmail.com \
    --to=cliff.brake@gmail.com \
    --cc=openembedded-devel@lists.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