On Sun, Apr 24, 2011 at 1:27 PM, Zach Pfeffer wrote:
> We're planning on bringing up Gerrit at UDS for tracking Android
> upstreaming. Perhaps it could be used for tracking GCC patches?
Probably not. It seems to be tied to git and requires the Android
workflow. Here's our workflow:
Patches tha
We're planning on bringing up Gerrit at UDS for tracking Android
upstreaming. Perhaps it could be used for tracking GCC patches?
On Tue, Apr 19, 2011 at 4:22 PM, James Westby wrote:
> On Wed, 13 Apr 2011 14:54:55 +1200, Michael Hope
> wrote:
>> Hmm. We already do patch tracking in Linaro GCC t
On Wed, 13 Apr 2011 14:54:55 +1200, Michael Hope
wrote:
> Hmm. We already do patch tracking in Linaro GCC to make sure that all
> patches go upstream. It's a manual process as the GCC workflow itself
> is very manual.
>
> I don't want to manually update two places when a patch changes state.
>
On Wed, 2011-04-13 at 14:54 +1200, Michael Hope wrote:
> On Sat, Apr 9, 2011 at 2:14 AM, James Westby wrote:
> > Hi,
> >
> > This service is going to be used by management to get an idea of the
> > number of patches going to each project over time, the number of patches
> > submitted upstream by e
On Sat, Apr 9, 2011 at 2:14 AM, James Westby wrote:
> Hi,
>
> This service is going to be used by management to get an idea of the
> number of patches going to each project over time, the number of patches
> submitted upstream by each team over time, the % of patches accepted
> upstream, the avera
On Fri, 2011-04-08 at 18:24 +0100, Peter Maydell wrote:
> On 8 April 2011 17:15, James Westby wrote:
> > On Fri, 8 Apr 2011 16:41:26 +0100, Peter Maydell
> > wrote:
> >> On 8 April 2011 15:14, James Westby wrote:
[...]
>
> >> In that case I'd like it to be able to replace my
> >> manual wiki-b
On Fri, 2011-04-08 at 16:25 +0200, Alexander Sack wrote:
> On Fri, Apr 8, 2011 at 4:14 PM, James Westby wrote:
> > Hi,
> >
> > This service is going to be used by management to get an idea of the
> > number of patches going to each project over time, the number of patches
> > submitted upstream by
On 9 April 2011 00:25, Alexander Sack wrote:
> On Fri, Apr 8, 2011 at 4:14 PM, James Westby wrote:
>> Now is the time to speak up if the interface doesn't have what you need
>> to do this. Obviously it would be better if it took care of everything
>> for you, but we don't think that everything c
On Fri, 8 Apr 2011 18:24:03 +0100, Peter Maydell
wrote:
> Sure. It does mean that fixing deficiencies in the system is more
> important than if it's just collecting patches and only needs to
> be interacted with by a few people.
Agreed.
> It's a feature I'd really like to see, and upstream soun
On 8 April 2011 17:15, James Westby wrote:
> On Fri, 8 Apr 2011 16:41:26 +0100, Peter Maydell
> wrote:
>> On 8 April 2011 15:14, James Westby wrote:
>> > This service is going to be used by management to get an idea of the
>> > number of patches going to each project over time, the number of pa
On Fri, 8 Apr 2011 16:41:26 +0100, Peter Maydell
wrote:
> On 8 April 2011 15:14, James Westby wrote:
> > This service is going to be used by management to get an idea of the
> > number of patches going to each project over time, the number of patches
> > submitted upstream by each team over time
On 8 April 2011 15:14, James Westby wrote:
> This service is going to be used by management to get an idea of the
> number of patches going to each project over time, the number of patches
> submitted upstream by each team over time, the % of patches accepted
> upstream, the average time from subm
On Fri, Apr 8, 2011 at 4:14 PM, James Westby wrote:
> Hi,
>
> This service is going to be used by management to get an idea of the
> number of patches going to each project over time, the number of patches
> submitted upstream by each team over time, the % of patches accepted
> upstream, the avera
Hi,
This service is going to be used by management to get an idea of the
number of patches going to each project over time, the number of patches
submitted upstream by each team over time, the % of patches accepted
upstream, the average time from submission to acceptance for each
project, and othe
On 7 April 2011 16:04, Guilherme Salgado wrote:
> On Thu, 2011-04-07 at 16:01 +0100, Peter Maydell wrote:
>> but when I sign into this patchwork via openid it only knows about
>> the chiark one, not the linaro one.
>
> That's because Launchpad only sends us your preferred email address when
> you
On Thu, 2011-04-07 at 16:01 +0100, Peter Maydell wrote:
> On 7 April 2011 15:45, Guilherme Salgado wrote:
>
> > - Not all of your patches may be shown under /user/submitted. if that's
> > the case, make sure all your email addresses are registered in Launchpad
> > as we're sucking that data from
16 matches
Mail list logo
