[new project] Request to add project 'LNG Kernel'

[Mike Holmes]

Name: Name 'LNG Kernel'
Mailing List: <email address hidden> - google group
Source Tree: ssh://<email address hidden>/kernel/linux-linaro-lng.git there are two branches that matter linux-lng & linux-lng-preempt-rt

[Milo Casagrande (milo)]

Hi Mike,

unfortunately, tracking branches other than master is not possible.
Patchwork requirements for a new project are:
- a mailing list address, and one mailing list per project
- a single git tree, with a single branch for each project

We also can't use multiple branches.

This is reflecting the workflow that patchwork was intended for: kernel development, where a project is made of a single mailing list, a single tree and the master branch where everything lands eventually.

Is the work done on that Linaro git tree ending up also on the upstream tree?

[Mike Holmes (mike-holmes)]

These changes can end up upstream, but we really wanted a way to try to
make it easy to understand the current state of things in our trees.
knowing which patches are discarded or under review for those branches
would be really useful.

It looks like patches can't really help us.

Thanks!
Mike

On 19 February 2014 03:45, Milo Casagrande <email address hidden>wrote:

> Hi Mike,
>
> unfortunately, tracking branches other than master is not possible.
> Patchwork requirements for a new project are:
> - a mailing list address, and one mailing list per project
> - a single git tree, with a single branch for each project
>
> We also can't use multiple branches.
>
> This is reflecting the workflow that patchwork was intended for: kernel
> development, where a project is made of a single mailing list, a single
> tree and the master branch where everything lands eventually.
>
> Is the work done on that Linaro git tree ending up also on the upstream
> tree?
>
> ** Changed in: linaro-patchmetrics
> Status: New => Incomplete
>
> ** Changed in: linaro-patchmetrics
> Importance: Undecided => Low
>
> ** Changed in: linaro-patchmetrics
> Assignee: (unassigned) => Milo Casagrande (milo)
>
> ** Changed in: linaro-patchmetrics
> Milestone: None => 2014.02
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1281868
>
> Title:
> [new project] Request to add project 'LNG Kernel'
>
> Status in Linaro patch metrics:
> Incomplete
>
> Bug description:
> Name: Name 'LNG Kernel'
> Mailing List: <email address hidden> - google group
> Source Tree: ssh://<email address hidden>/kernel/linux-linaro-lng.gitthere are two branches that matter linux-lng & linux-lng-preempt-rt
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linaro-patchmetrics/+bug/1281868/+subscriptions
>

[Milo Casagrande (milo)]

On Wed, Feb 19, 2014 at 6:30 PM, Mike Holmes <email address hidden> wrote:
> These changes can end up upstream, but we really wanted a way to try to
> make it easy to understand the current state of things in our trees.
> knowing which patches are discarded or under review for those branches
> would be really useful.

Consider that patches.l.o is meant to track upstream work, it should
not be used as a tool to track internal work.
I see this topic coming up more and more, it might be good to discuss
at Connect.

--
Milo Casagrande
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs