All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: MINUTES: OE-TSC meeting 29-Sep-2011
Date: Fri, 30 Sep 2011 13:21:36 -0700	[thread overview]
Message-ID: <1317414101.11645.26.camel@scimitar> (raw)
In-Reply-To: <CABcZANk3bjhA0mOzroWkx_M+YH1f01Pq9WjkgURah1yMNi_EdA@mail.gmail.com>

On Fri, 2011-09-30 at 13:08 -0700, Chris Larson wrote:
> On Fri, Sep 30, 2011 at 12:59 PM, Joshua Lock <josh@linux.intel.com> wrote:
> > On Fri, 2011-09-30 at 11:16 -0700, Chris Larson wrote:
> >> On Fri, Sep 30, 2011 at 11:14 AM, Jeff Osier-Mixon <jefro@jefro.net> wrote:
> >> > 1. Jefro
> >> > 2. a. some minutes not making it to mailing list, Jefro to post on wiki
> >> >    b. yocto evaluating gerrit, possible patchwork replacement for OE, khem
> >> > will research
> >>
> >> ReviewBoard may be worth looking at as an alternative to gerritt, as well.
> >
> > I think people like PatchWork and Gerrit because of their command line
> > tools - do you know if ReviewBoard has cli tools too?
> 
> It does, yeah. I don't have a lot of personal experience with either
> one, but I think we should evaluate both.

Good to know, I concur!

Joshua
-- 
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre




  reply	other threads:[~2011-09-30 20:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 18:14 MINUTES: OE-TSC meeting 29-Sep-2011 Jeff Osier-Mixon
2011-09-30 18:14 ` Jeff Osier-Mixon
2011-09-30 18:16 ` Chris Larson
2011-09-30 19:59   ` Joshua Lock
2011-09-30 20:08     ` Chris Larson
2011-09-30 20:21       ` Joshua Lock [this message]
2011-10-03 19:25   ` Khem Raj
2011-10-03 21:53   ` Saul Wold
2011-10-03 21:56     ` Chris Larson

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=1317414101.11645.26.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.