From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Joshua Lock <joshua.lock@collabora.co.uk>, yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi] RFC on choice of tool for patch review
Date: Wed, 12 Aug 2015 10:54:10 +0100 [thread overview]
Message-ID: <55CB17C2.1000201@dynamicdevices.co.uk> (raw)
In-Reply-To: <1439372740.2733.4.camel@collabora.co.uk>
On 12/08/2015 10:45, Joshua Lock wrote:
> On Wed, 2015-08-12 at 10:25 +0100, Joshua Lock wrote:
>> On Wed, 2015-08-12 at 10:17 +0100, Alex J Lennon wrote:
>>> We've been having a discussion on a way forward to manage patches
>>> and
>>> code review and would like to open this up for discussion to agree
>>> a
>>> way
>>> forward.
>> There's http://patchwork.openembedded.org/. I'm not sure who
>> maintains
>> it, nor if anyone uses it, but patches sent to the mailing list end
>> up
>> there.
>>
>> OOI who are "we" in this context? What benefits would a change bring?
> I managed to miss both the [yocto] and [meta-raspberrypi] tags on this
> mail, apologies for that. I guess that "we" are the meta-raspberrypi
> maintainers.
Yes :)
Andrei (maintainer) was using Gerrit but that went away for reasons
outlined in the preceding email.
Some visibility and control of the review process has been lost as a
result and so it was suggested we kick off a conversation on what
tooling to use to restore that.
> Still, the patchwork instance may be an option? The meta-freescale
> layers appear to be using it.
Many thanks!
Cheers,
Alex
prev parent reply other threads:[~2015-08-12 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 9:17 [meta-raspberrypi] RFC on choice of tool for patch review Alex J Lennon
2015-08-12 9:25 ` Joshua Lock
2015-08-12 9:45 ` Joshua Lock
2015-08-12 9:54 ` Alex J Lennon [this message]
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=55CB17C2.1000201@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=joshua.lock@collabora.co.uk \
--cc=yocto@yoctoproject.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.