On 18/08/10 22:36, Michael Hope wrote:
> You can tell which revisions are untracked by the patchtracker report
> at http://ex.seabright.co.nz/helpers/patchtrack. Revisions that are
> currently untracked can be added to an existing ticket by adding a one
> line 'related:' comment to that ticket, or
I've had a go at adding the basic trackerbot functionality to:
http://ex.seabright.co.nz/helpers/patchtrack
This page lists all revisions on a branch. Any revisions that don't
have a corresponding ticket are marked in orange and have a 'Create
one' link. Clicking this link takes you to a pre-f
On Wed, Aug 18, 2010 at 8:11 PM, Andrew Stubbs wrote:
> On 17/08/10 23:38, Michael Hope wrote:
>>
>> Hi Andrew. I'm confused - apart from a few differences, our methods
>> seem to be the same.
>>
>> The differences against Method 1 are:
>> 1. Every revision has an associated ticket
>> 2. There'
On 17/08/10 23:38, Michael Hope wrote:
> Hi Andrew. I'm confused - apart from a few differences, our methods
> seem to be the same.
>
> The differences against Method 1 are:
> 1. Every revision has an associated ticket
> 2. There's a bot that automatically creates a ticket per revision
Yes, b
Hi Andrew. I'm confused - apart from a few differences, our methods
seem to be the same.
The differences against Method 1 are:
1. Every revision has an associated ticket
2. There's a bot that automatically creates a ticket per revision
3. Final upstream status is tracked through the status fie
On 17/08/10 10:39, Andrew Stubbs wrote:
> I really wanted this done weeks ago (when I originally implemented it),
> so I'm now getting frustrated that every time it looks like we're
> getting somewhere, it seems to have gone off on a tangent and lost sight
> of all the original requirements.:(
In
On 17/08/10 10:39, Andrew Stubbs wrote:
> I'm going to write a "method 2" to explain what I need/want.
Now done:
https://wiki.linaro.org/WorkingGroups/ToolChain/PatchTracking#Method%202
Andrew
___
linaro-toolchain mailing list
linaro-toolchain@lists.li
On 17/08/10 00:23, Michael Hope wrote:
> Thoughts?
This isn't what we discussed at all
Yes, keeping a bug open to track work begun upstream is probably a good
policy, but it's not at all what we were discussing.
The patch tracker should ensure that all revisions in the bzr branch are
subm
On Tue, Aug 17, 2010, Michael Hope wrote:
> Thoughts?
Looks good!
--
Loïc Minier
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
