With gerrit have the ability to pull patch sets build and test.
On Apr 29, 2013 10:04 PM, "Mark Brown" wrote:
> On Mon, Apr 29, 2013 at 09:28:16AM -0400, Christopher Covington wrote:
>
> > I'm familiar with a submit- or merge-time option for this. It's not
> clear to
> > me from your reply whethe
On Mon, Apr 29, 2013 at 09:28:16AM -0400, Christopher Covington wrote:
> I'm familiar with a submit- or merge-time option for this. It's not clear to
> me from your reply whether you're referring to this or an upload- or push-time
> option.
Oh, on initial push? I've not seen that but it does str
On 04/29/2013 09:28 AM, Christopher Covington wrote:
> On 04/28/2013 06:18 AM, Mark Brown wrote:
>> On Wed, Apr 17, 2013 at 09:14:54AM -0400, Christopher Covington wrote:
>>> On 04/17/2013 06:29 AM, Jon Medhurst (Tixy) wrote:
>>
And with gerrit the patch author needs to get an account enabled
On 04/28/2013 06:18 AM, Mark Brown wrote:
> On Wed, Apr 17, 2013 at 09:14:54AM -0400, Christopher Covington wrote:
>> On 04/17/2013 06:29 AM, Jon Medhurst (Tixy) wrote:
>
>>> And with gerrit the patch author needs to get an account enabled with the
>>> project, produce a git commit against the cur
On Wed, Apr 17, 2013 at 09:14:54AM -0400, Christopher Covington wrote:
> On 04/17/2013 06:29 AM, Jon Medhurst (Tixy) wrote:
> > And with gerrit the patch author needs to get an account enabled with the
> > project, produce a git commit against the current tip,
> I can't recall ever seeing an uplo
Christopher Covington writes:
> On 04/17/2013 06:29 AM, Jon Medhurst (Tixy) wrote:
>> On Wed, 2013-04-17 at 06:21 +0200, Jonathan Aquilina wrote:
>>> Doesnt email run the risk of a patch slipping through the cracks?
>>
>> And with gerrit the patch author needs to get an account enabled with the
I have seen gerrit in use with libreoffice, they have it setup to where you
have build bot machines which can automatically pull a patch make a build
and test the patch with the build to see if it builds successfully.
Also, with gerrit you dont need to assign reviewers people that have the
abilit
On Wed, 2013-04-17 at 09:14 -0400, Christopher Covington wrote:
> Hi Jon,
>
> On 04/17/2013 06:29 AM, Jon Medhurst (Tixy) wrote:
> > On Wed, 2013-04-17 at 06:21 +0200, Jonathan Aquilina wrote:
> >> Doesnt email run the risk of a patch slipping through the cracks?
> >
> > And with gerrit the patch
Hi Jon,
On 04/17/2013 06:29 AM, Jon Medhurst (Tixy) wrote:
> On Wed, 2013-04-17 at 06:21 +0200, Jonathan Aquilina wrote:
>> Doesnt email run the risk of a patch slipping through the cracks?
>
> And with gerrit the patch author needs to get an account enabled with the
> project, produce a git comm
On Wed, 2013-04-17 at 06:21 +0200, Jonathan Aquilina wrote:
> Doesnt email run the risk of a patch slipping through the cracks?
And with gerrit the patch author needs to get an account enabled with
the project, produce a git commit against the current tip, know who to
pick as reviewers then rely o
Totally under stand :). Hopefully come summer I will be able to get my
hands on a board and start contributing :)
On Wed, Apr 17, 2013 at 9:51 AM, Nicolas Dechesne <
nicolas.deche...@linaro.org> wrote:
> On Wed, Apr 17, 2013 at 6:21 AM, Jonathan Aquilina
> wrote:
> > Doesnt email run the risk o
On Wed, Apr 17, 2013 at 6:21 AM, Jonathan Aquilina
wrote:
> Doesnt email run the risk of a patch slipping through the cracks?
as highlighted by Deepak above, each project will use the
processes/methods inherited from its 'upstream'. That's why gerrit is
being used for Android activities for examp
Doesnt email run the risk of a patch slipping through the cracks?
On Tue, Apr 16, 2013 at 9:02 PM, Deepak Saxena wrote:
> On 16 April 2013 07:06, Jonathan Aquilina wrote:
> > Wouldnt all of them benefit in a way from it?
>
> My take on this is that one of the goals of Linaro's assignee process
On 16 April 2013 07:06, Jonathan Aquilina wrote:
> Wouldnt all of them benefit in a way from it?
My take on this is that one of the goals of Linaro's assignee process
is to teach folks how to work in the open source community and than
take that knowledge back to internal teams. This means we shou
Wouldnt all of them benefit in a way from it?
On Tue, Apr 16, 2013 at 4:04 PM, Nicolas Dechesne <
nicolas.deche...@linaro.org> wrote:
> On Tue, Apr 16, 2013 at 3:59 PM, Jonathan Aquilina
> wrote:
> > Have you guys considered gerrit code review for patches? as well as
> setting
> > up build bots
On Tue, Apr 16, 2013 at 3:59 PM, Jonathan Aquilina
wrote:
> Have you guys considered gerrit code review for patches? as well as setting
> up build bots to test build the patches?
which projects at Linaro you have in mind for this request? it's
already being used for Android 'stuff', see
http://r
Have you guys considered gerrit code review for patches? as well as setting
up build bots to test build the patches?
--
Jonathan Aquilina
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
On 21 February 2013 16:34, Amit Kucheria wrote:
> I don't have a strong preference one way or another about switching
> from linaro-dev to linaro-kernel.
>
> Don't forget to update
> https://wiki.linaro.org/Resources/HowTo/Git/GitSendEmail
Done.
___
l
On Thu, Feb 21, 2013 at 4:27 PM, Viresh Kumar wrote:
> On 18 February 2013 23:50, Serge Broslavsky
> wrote:
>> On 18.02.13 12:20 -0500, Nicolas Pitre wrote:
>>> For the record, I think what Peter is suggesting is reasonable. There
>>> must be better ways for people to find out what Linaro is par
On 18 February 2013 23:50, Serge Broslavsky wrote:
> On 18.02.13 12:20 -0500, Nicolas Pitre wrote:
>> For the record, I think what Peter is suggesting is reasonable. There
>> must be better ways for people to find out what Linaro is participating in
>> other than scaring them away from linaro-dev
On 18.02.13 12:20 -0500, Nicolas Pitre wrote:
> On Mon, 18 Feb 2013, Amit Kucheria wrote:
>
> > Since Peter and I were discussing this on IRC that led to this email,
> > here is a bit of context on the current behaviour:
> >
> > On Mon, Feb 18, 2013 at 8:16 PM, Peter Maydell
> > wrote:
> > > Hi
On Mon, 18 Feb 2013, Amit Kucheria wrote:
> Since Peter and I were discussing this on IRC that led to this email,
> here is a bit of context on the current behaviour:
>
> On Mon, Feb 18, 2013 at 8:16 PM, Peter Maydell
> wrote:
> > Hi; does anybody else think it would be a good idea to move all
Since Peter and I were discussing this on IRC that led to this email,
here is a bit of context on the current behaviour:
On Mon, Feb 18, 2013 at 8:16 PM, Peter Maydell wrote:
> Hi; does anybody else think it would be a good idea to move all
> the kernel patch email traffic off linaro-dev and onto
Hi; does anybody else think it would be a good idea to move all
the kernel patch email traffic off linaro-dev and onto a more
kernel-specific mailing list (eg, linaro-kernel, maybe) ?
A quick eyeball of a few pages of my gmail folder for linaro-dev
shows that something like 75% of it is kernel dev
On Sat, October 22, 2011 3:52 pm, Konstantinos Margaritis wrote:
> On 22 October 2011 16:17, Joop Boonen wrote:
>> Hi all,
>>
>> Most of the (ARM) distros are currently working on or in the transition
>> to
>> hardfp, but until now most GPU's in de ARM Cortex SOCs don't have any
>> hardfp drivers
On Tue, Aug 30, 2011 at 9:55 PM, Ricardo Salveti
wrote:
> Hey all,
>
> As we're having the Linaro Connect Q4.11 together with UDS-P, would
> like to know if there is any special topic it'd be useful to cover as
> a summit there.
>
> Any ARM related topics that might be related with cross-distro
>
Hey all,
As we're having the Linaro Connect Q4.11 together with UDS-P, would
like to know if there is any special topic it'd be useful to cover as
a summit there.
Any ARM related topics that might be related with cross-distro
collaboration or just related with Ubuntu/Debian should fit.
Some sugg
27 matches
Mail list logo
