Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Patch merge process
Date: Tue, 8 Sep 2015 23:06:42 +0200	[thread overview]
Message-ID: <20150908210642.GG2381@jama> (raw)
In-Reply-To: <CAMKF1sogs9sRR_07nOxZrvvOxXj_=ioqNr=_vN+hr+VFf2BO6A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

On Tue, Sep 08, 2015 at 11:39:17AM -0700, Khem Raj wrote:
> On Tue, Sep 8, 2015 at 11:18 AM, Trevor Woerner <twoerner@gmail.com> wrote:
> > If Richard doesn't want to use gerrit for OE-core, that doesn't exclude
> > others from using it for the layers they manage, does it?
> 
> yes, however, we should prefer this to run on oe domain, its better
> for project and then if most of layers use it its fine too, it could
> end up
> with same situation as patchwork where oe-core and bitbake do not use
> it actively. other layers do. its not ideal situation but its ok as
> long as
> its makes people productive, we could be open for options its matter
> of volunteers then maintaining the infra for these services.

I agree, there are not technical reasons for not using it for other
layers, but once we ask contributors to create account on gerrit and
submit all patches through gerrit for *some* layers, then these people
will ask why oe-core and bitbake submissions are different.

I should also say that I really like gerrit work-flow and review, but if
people continue to send patches to e-mail and someone else will need to
add Change-Ids to them and consolidate them into review-chains, than
it's not as great as it could be if all related people "buy-it" and use
it exclusively.

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-09-08 21:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 17:40 Patch merge process Khem Raj
2015-09-01 20:04 ` Richard Purdie
2015-09-01 23:17   ` Khem Raj
2015-09-02  7:31     ` Richard Purdie
2015-09-02 20:29       ` Martin Jansa
2015-09-01 21:55 ` Martin Jansa
2015-09-01 22:05   ` Otavio Salvador
2015-09-01 22:46     ` Khem Raj
2015-09-01 22:51       ` Otavio Salvador
2015-09-02  7:09         ` Richard Purdie
2015-09-08 18:18           ` Trevor Woerner
2015-09-08 18:39             ` Khem Raj
2015-09-08 21:06               ` Martin Jansa [this message]
2015-09-10 14:05                 ` Alexander Kanevskiy
     [not found]                 ` <CANFkWp=w7Lj_M4hPdBjNya+EHd_9oMJ9QM-ewGO2AAsxJs-9uA@mail.gmail.com>
2015-09-10 14:18                   ` Martin Jansa
2015-09-10 15:23                     ` Alexander Kanevskiy
2015-09-10 15:39                       ` Martin Jansa
2015-09-10 16:55                         ` Otavio Salvador
2015-09-01 22:45   ` Khem Raj

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=20150908210642.GG2381@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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