On Sun, 2011-08-28 at 10:35 +0800, Andy Green wrote:
> On 08/28/2011 05:20 AM, Somebody in the thread at some point said:
> > But I've got an open mind and am willing to try it out and figure out a
> > workflow. I suspect for me it really won't be anything other then a
> > different location to "gi
On 08/28/2011 05:20 AM, Somebody in the thread at some point said:
On Sat, 2011-08-27 at 21:29 +0800, Andy Green wrote:
On 08/27/2011 02:15 AM, Somebody in the thread at some point said:
Gerrit is that it doesn't care if the tree has been rebased. It will
just try and merge the changeset on top
On Sat, 2011-08-27 at 21:29 +0800, Andy Green wrote:
> On 08/27/2011 02:15 AM, Somebody in the thread at some point said:
> > Gerrit is that it doesn't care if the tree has been rebased. It will
> > just try and merge the changeset on top of the current tree, whatever
> > the history so in that cas
On 08/27/2011 02:15 AM, Somebody in the thread at some point said:
How well what are basically externally generated and managed kernels will
fit into Gerrit flow is something I don't really understand. But I don't
think it will be as simple as the case where the kernel is a history tree
managed
Hello Zach,
On Thu, 25 Aug 2011 18:12:01 -0500
Zach Pfeffer wrote:
[]
> > I also updated Linaro Gerrit howto:
> > https://wiki.linaro.org/Platform/Android/Gerrit , which now should
> > have all info to have one started quickly with Gerrit, and cover
> > all aspects of Gerrit setup (like upstream
On 26 August 2011 00:04, Andy Green wrote:
> On 08/26/2011 12:12 AM, Somebody in the thread at some point said:
>
>>> 1. Set up branch policy (naming, etc.) and enforce it on Gerrit level.
>>> This may require revamping branching in other toolchain/* components
>>> (upstreamed not from AOSP), but
On 08/26/2011 12:12 AM, Somebody in the thread at some point said:
1. Set up branch policy (naming, etc.) and enforce it on Gerrit level.
This may require revamping branching in other toolchain/* components
(upstreamed not from AOSP), but in the end we'll get really robust
development setup.
A
On 23 August 2011 07:46, Paul Sokolovsky wrote:
> Hello,
>
> Some time passed since last update on Gerrit deployment, that's
> because work on complete AOSP mirroring to out tree took longer than
> expected. All in all, following was done:
>
> Revamped branching in
Hello,
Some time passed since last update on Gerrit deployment, that's
because work on complete AOSP mirroring to out tree took longer than
expected. All in all, following was done:
Revamped branching in our toolchain/* components, freed room for
upstream branches, mirrored them.
Mirrored
