Re: Please help us setup patches.linaro.org

2011-06-22 Thread Dave Martin 
On Tue, Jun 21, 2011 at 03:27:07PM -0300, Guilherme Salgado wrote:
> Hi Dave,
> 
> Thanks for reporting it.  This was fallout from when IS restarted the
> machine to add more disk, and they're working on it right now. It should
> be fixed RSN.

It seems to be working again now.

Thanks!
---Dave

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-21 Thread Guilherme Salgado 
Hi Dave,

Thanks for reporting it.  This was fallout from when IS restarted the
machine to add more disk, and they're working on it right now. It should
be fixed RSN.

Cheers,

On Tue, 2011-06-21 at 18:10 +0100, Dave Martin wrote:
> Hi there,
> 
> Login on patches.linaro.org appears broken.  When I try to log in, I get this:
> 
> OpenID failed
> 
> OpenID discovery error: Error fetching XRDS document: (28, 'connect()
> timed out!')
> 
> This has been happening for about 2 days, but it was working prior to that.
> 
> Cheers
> ---Dave

-- 
Guilherme Salgado 


signature.asc
Description: This is a digitally signed message part
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-21 Thread Dave Martin 
Hi there,

Login on patches.linaro.org appears broken.  When I try to log in, I get this:

OpenID failed

OpenID discovery error: Error fetching XRDS document: (28, 'connect()
timed out!')

This has been happening for about 2 days, but it was working prior to that.

Cheers
---Dave

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-21 Thread Daniel Lezcano 

On 06/21/2011 03:09 PM, Guilherme Salgado wrote:

On Tue, 2011-06-21 at 11:23 +0200, Daniel Lezcano wrote:

On 06/16/2011 07:42 PM, Guilherme Salgado wrote:


[ ... ]


We can use powerdebug as a guinea pig for this and if it works fine we
can do it for others. Do you know who we should talk to in order to get
this done?

Hi Guilherme,

I have no problem to use powerdebug to validate this approach.

Did you asked to the mailman administrator [1] to add a powerdebug email
alias for linaro-dev ?

I was thinking of having powerde...@linaro.org as a regular mail account
forwarding everything to linaro-dev@lists.linaro.org; that wouldn't need
to be done on mailman.  Do you see any reason for doing it on mailman?
Maybe powerde...@lists.linaro.org would make more sense?


I can't create a powerde...@linaro.org or powerde...@lists.linaro.org 
mail address.

We should ask to the mailman admin or IT what is the better approach.

I Cc'ed Amit which is the tech lead of the power management team.

Amit ?

we would like, Guilherme and I, to create a specific mail address for 
powerdebug so patchwork can correctly put the patches to the right 
project instead of "other-unknown".


We thought we can create a mailing list for powerdebug and subscribe 
only the linaro-dev mailing list. When we send the patches to 
powerde...@linaro.org, cc'ing patc...@linaro.org.
The latter will determine to which project the patches belong to and at 
the same time the patches will fall into the linaro-dev mailing list.


If the result is what we expect with powerdebug, Guilherme would like to 
extend this approach to all linaro projects.


What do you think ?

Thanks
  -- Daniel


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-21 Thread Guilherme Salgado 
On Tue, 2011-06-21 at 11:23 +0200, Daniel Lezcano wrote:
> On 06/16/2011 07:42 PM, Guilherme Salgado wrote:
> 
> 
> [ ... ]
> 
> > We can use powerdebug as a guinea pig for this and if it works fine we
> > can do it for others. Do you know who we should talk to in order to get
> > this done?
> 
> Hi Guilherme,
> 
> I have no problem to use powerdebug to validate this approach.
> 
> Did you asked to the mailman administrator [1] to add a powerdebug email 
> alias for linaro-dev ?

I was thinking of having powerde...@linaro.org as a regular mail account
forwarding everything to linaro-dev@lists.linaro.org; that wouldn't need
to be done on mailman.  Do you see any reason for doing it on mailman?
Maybe powerde...@lists.linaro.org would make more sense?

Cheers,

-- 
Guilherme Salgado 


signature.asc
Description: This is a digitally signed message part
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-21 Thread Daniel Lezcano 

On 06/16/2011 07:42 PM, Guilherme Salgado wrote:


[ ... ]


We can use powerdebug as a guinea pig for this and if it works fine we
can do it for others. Do you know who we should talk to in order to get
this done?


Hi Guilherme,

I have no problem to use powerdebug to validate this approach.

Did you asked to the mailman administrator [1] to add a powerdebug email 
alias for linaro-dev ?


[1]  http://lists.linaro.org/mailman/listinfo/mailman

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-16 Thread Michael Hope 
On Thu, Jun 16, 2011 at 1:26 AM, Guilherme Salgado
 wrote:
> Hi folks,
>
> http://patches.linaro.org/ went live yesterday and we need your help to
> set it up and get accurate metrics. It should take only a few minutes!
>
> The first thing we need is the HTTP URL for the upstream master branch
> of every project on the front page -- I'll take a git:// URL if that's
> all they have.  If you could send me the URLs for the projects you
> contribute to, it'd be great. This has to be done only once and we'll
> use that to automatically detect when a patch is committed upstream.

Hi.  I've updated the page at:
 https://wiki.linaro.org/WorkingGroups/ToolChain/CodeImports

with links to the primary projects we work on and a few secondary
ones.  Note that only QEMU natively uses GIT.  Most have a GIT mirror
though.

-- Michael

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-16 Thread Daniel Lezcano 

On 06/16/2011 07:42 PM, Guilherme Salgado wrote:

On Thu, 2011-06-16 at 16:38 +0200, Daniel Lezcano wrote:

On 06/16/2011 02:45 PM, Guilherme Salgado wrote:

On Thu, 2011-06-16 at 00:16 +0200, Daniel Lezcano wrote:

On 06/15/2011 03:26 PM, Guilherme Salgado wrote:

Hi folks,

http://patches.linaro.org/ went live yesterday and we need your help to
set it up and get accurate metrics. It should take only a few minutes!

The first thing we need is the HTTP URL for the upstream master branch
of every project on the front page -- I'll take a git:// URL if that's
all they have.  If you could send me the URLs for the projects you
contribute to, it'd be great. This has to be done only once and we'll
use that to automatically detect when a patch is committed upstream.

http://git.linaro.org/git/tools/powerdebug.git

http://git.linaro.org/git/tools/pm-qa.git

I've created new projects for those two. Thanks!

Thanks.

By the way, I am working for Linaro since one month, I missed I should
have sent two patchset to linaro-dev@ cc'ing patches@l.o

Is there a way to "import" these patchsets into patches.linaro.org ?

http://lists.linaro.org/pipermail/linaro-dev/2011-June/004957.html
http://lists.linaro.org/pipermail/linaro-dev/2011-May/004575.html

The only way to do that is to send them to patches@l.o. If you have the
git branch where they came from handy you could git send-email them
again?


Yes, sure. That will not really reflect the posting dates but I suppose 
it is better than nothing.



[ ... ]


Similarly, if any of the patches you see there have been superseded or
rejected, please do mark them as such. You can do bulk changes there
selecting the patches and using the form at the bottom.

Finally, although we do our best to place patches under the appropriate
projects, sometimes we're not able to (e.g. when patches are sent *only*
to patches@l.o), and in these cases they need to be moved manually. The
list of patches for which we couldn't find a project are at

 http://patches.linaro.org/patchwork/project/other-unknown/list/

The two projects are hosted at git.linaro.org and belongs to linaro. The
mailing list is linaro-dev@. If I understood correctly with this email
address you can't find to which project the patchset I will send for
powerdebug is related to, right ?

Yep, that's correct.


I sent a patchset with "powerdebug" keyword in the subject prefix.
Assuming you create the "powerdebug" project, will the next patchset go
to the right project ? Or do I have to move the patchset to the right
project manually using the form ?

We don't do that right now, so yes, you'll need to move them using the
form. However, I think it'd be possible to match the prefix to an
existing project when all else fails. A custom email header would be
more robust but I understand that a prefix is probably easier to use.
What do you think?

I don't know how to build a custom email header for git-send-email :/

I think a subject prefix is the easier way for now.

Maybe that could be nice to create a mailing list per linaro project and
subscribe only linaro-dev@ to these.

Each mailing list could be configured with the project prefix, so we
don't need to prefix the patches manually, that will be done
automatically when redirecting the mail to linaro-dev@, so people can
know what project we are talking about. I guess some configuration
should be done to prevent email ping-pong between linaro-dev and the
other projects mailing list.


Example:
I send a patch
  --to powerde...@linaro.org
  --cc patc...@linaro.org
  --subject "[ PATCH 1/1 ] hello world"

linaro-dev@ will receive :
  -- subject "[ powerdebug ][ PATCH 1/1 ] hello world"

patc...@linaro.org will receive :
  -- subject: "[ PATCH 1/1 ] hello world"

And you have the right --to email address to find the project the
patches are related to.

No ?

Yep, that would work just as you describe.


ps : the mail aliases could be used for linaro-dev instead of a mailing
list per project

And this makes it fairly easy to implement, but either way people will
have to remember to send the patches to the project alias (which is very
easy to remember, anyway) instead of linaro-dev@.


Yeah, if they send to the wrong address the patches will go to "unknow" 
and that will end up to the senders to move the patches to the right 
project.



We can use powerdebug as a guinea pig for this and if it works fine we
can do it for others. Do you know who we should talk to in order to get
this done?


I think we can create a mailing list [1] but an alias is better IMO. The 
latter should fall under the IT umbrella. Maybe we can ask to 
mail...@lists.linaro.org ...


[1] http://lists.linaro.org/mailman/create


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-16 Thread Guilherme Salgado 
On Thu, 2011-06-16 at 16:38 +0200, Daniel Lezcano wrote:
> On 06/16/2011 02:45 PM, Guilherme Salgado wrote:
> > On Thu, 2011-06-16 at 00:16 +0200, Daniel Lezcano wrote:
> >> On 06/15/2011 03:26 PM, Guilherme Salgado wrote:
> >>> Hi folks,
> >>>
> >>> http://patches.linaro.org/ went live yesterday and we need your help to
> >>> set it up and get accurate metrics. It should take only a few minutes!
> >>>
> >>> The first thing we need is the HTTP URL for the upstream master branch
> >>> of every project on the front page -- I'll take a git:// URL if that's
> >>> all they have.  If you could send me the URLs for the projects you
> >>> contribute to, it'd be great. This has to be done only once and we'll
> >>> use that to automatically detect when a patch is committed upstream.
> >> http://git.linaro.org/git/tools/powerdebug.git
> >>
> >> http://git.linaro.org/git/tools/pm-qa.git
> > I've created new projects for those two. Thanks!
> 
> Thanks.
> 
> By the way, I am working for Linaro since one month, I missed I should 
> have sent two patchset to linaro-dev@ cc'ing patches@l.o
> 
> Is there a way to "import" these patchsets into patches.linaro.org ?
> 
> http://lists.linaro.org/pipermail/linaro-dev/2011-June/004957.html
> http://lists.linaro.org/pipermail/linaro-dev/2011-May/004575.html

The only way to do that is to send them to patches@l.o. If you have the
git branch where they came from handy you could git send-email them
again?

> 
> >> [ ... ]
> >>
> >>> Similarly, if any of the patches you see there have been superseded or
> >>> rejected, please do mark them as such. You can do bulk changes there
> >>> selecting the patches and using the form at the bottom.
> >>>
> >>> Finally, although we do our best to place patches under the appropriate
> >>> projects, sometimes we're not able to (e.g. when patches are sent *only*
> >>> to patches@l.o), and in these cases they need to be moved manually. The
> >>> list of patches for which we couldn't find a project are at
> >>>
> >>> http://patches.linaro.org/patchwork/project/other-unknown/list/
> >> The two projects are hosted at git.linaro.org and belongs to linaro. The
> >> mailing list is linaro-dev@. If I understood correctly with this email
> >> address you can't find to which project the patchset I will send for
> >> powerdebug is related to, right ?
> > Yep, that's correct.
> >
> >> I sent a patchset with "powerdebug" keyword in the subject prefix.
> >> Assuming you create the "powerdebug" project, will the next patchset go
> >> to the right project ? Or do I have to move the patchset to the right
> >> project manually using the form ?
> > We don't do that right now, so yes, you'll need to move them using the
> > form. However, I think it'd be possible to match the prefix to an
> > existing project when all else fails. A custom email header would be
> > more robust but I understand that a prefix is probably easier to use.
> > What do you think?
> 
> I don't know how to build a custom email header for git-send-email :/
> 
> I think a subject prefix is the easier way for now.
> 
> Maybe that could be nice to create a mailing list per linaro project and 
> subscribe only linaro-dev@ to these.
> 
> Each mailing list could be configured with the project prefix, so we 
> don't need to prefix the patches manually, that will be done 
> automatically when redirecting the mail to linaro-dev@, so people can 
> know what project we are talking about. I guess some configuration 
> should be done to prevent email ping-pong between linaro-dev and the 
> other projects mailing list.
> 
> 
> Example:
> I send a patch
>  --to powerde...@linaro.org
>  --cc patc...@linaro.org
>  --subject "[ PATCH 1/1 ] hello world"
> 
> linaro-dev@ will receive :
>  -- subject "[ powerdebug ][ PATCH 1/1 ] hello world"
> 
> patc...@linaro.org will receive :
>  -- subject: "[ PATCH 1/1 ] hello world"
> 
> And you have the right --to email address to find the project the 
> patches are related to.
> 
> No ?

Yep, that would work just as you describe.

> ps : the mail aliases could be used for linaro-dev instead of a mailing 
> list per project

And this makes it fairly easy to implement, but either way people will
have to remember to send the patches to the project alias (which is very
easy to remember, anyway) instead of linaro-dev@.

We can use powerdebug as a guinea pig for this and if it works fine we
can do it for others. Do you know who we should talk to in order to get
this done?

-- 
Guilherme Salgado 


signature.asc
Description: This is a digitally signed message part
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-16 Thread Daniel Lezcano 

On 06/16/2011 02:45 PM, Guilherme Salgado wrote:

On Thu, 2011-06-16 at 00:16 +0200, Daniel Lezcano wrote:

On 06/15/2011 03:26 PM, Guilherme Salgado wrote:

Hi folks,

http://patches.linaro.org/ went live yesterday and we need your help to
set it up and get accurate metrics. It should take only a few minutes!

The first thing we need is the HTTP URL for the upstream master branch
of every project on the front page -- I'll take a git:// URL if that's
all they have.  If you could send me the URLs for the projects you
contribute to, it'd be great. This has to be done only once and we'll
use that to automatically detect when a patch is committed upstream.

http://git.linaro.org/git/tools/powerdebug.git

http://git.linaro.org/git/tools/pm-qa.git

I've created new projects for those two. Thanks!


Thanks.

By the way, I am working for Linaro since one month, I missed I should 
have sent two patchset to linaro-dev@ cc'ing patches@l.o


Is there a way to "import" these patchsets into patches.linaro.org ?

http://lists.linaro.org/pipermail/linaro-dev/2011-June/004957.html
http://lists.linaro.org/pipermail/linaro-dev/2011-May/004575.html


[ ... ]


Similarly, if any of the patches you see there have been superseded or
rejected, please do mark them as such. You can do bulk changes there
selecting the patches and using the form at the bottom.

Finally, although we do our best to place patches under the appropriate
projects, sometimes we're not able to (e.g. when patches are sent *only*
to patches@l.o), and in these cases they need to be moved manually. The
list of patches for which we couldn't find a project are at

http://patches.linaro.org/patchwork/project/other-unknown/list/

The two projects are hosted at git.linaro.org and belongs to linaro. The
mailing list is linaro-dev@. If I understood correctly with this email
address you can't find to which project the patchset I will send for
powerdebug is related to, right ?

Yep, that's correct.


I sent a patchset with "powerdebug" keyword in the subject prefix.
Assuming you create the "powerdebug" project, will the next patchset go
to the right project ? Or do I have to move the patchset to the right
project manually using the form ?

We don't do that right now, so yes, you'll need to move them using the
form. However, I think it'd be possible to match the prefix to an
existing project when all else fails. A custom email header would be
more robust but I understand that a prefix is probably easier to use.
What do you think?


I don't know how to build a custom email header for git-send-email :/

I think a subject prefix is the easier way for now.

Maybe that could be nice to create a mailing list per linaro project and 
subscribe only linaro-dev@ to these.


Each mailing list could be configured with the project prefix, so we 
don't need to prefix the patches manually, that will be done 
automatically when redirecting the mail to linaro-dev@, so people can 
know what project we are talking about. I guess some configuration 
should be done to prevent email ping-pong between linaro-dev and the 
other projects mailing list.



Example:
I send a patch
--to powerde...@linaro.org
--cc patc...@linaro.org
--subject "[ PATCH 1/1 ] hello world"

linaro-dev@ will receive :
-- subject "[ powerdebug ][ PATCH 1/1 ] hello world"

patc...@linaro.org will receive :
-- subject: "[ PATCH 1/1 ] hello world"

And you have the right --to email address to find the project the 
patches are related to.


No ?

ps : the mail aliases could be used for linaro-dev instead of a mailing 
list per project



___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-16 Thread Guilherme Salgado 
On Thu, 2011-06-16 at 00:16 +0200, Daniel Lezcano wrote:
> On 06/15/2011 03:26 PM, Guilherme Salgado wrote:
> > Hi folks,
> >
> > http://patches.linaro.org/ went live yesterday and we need your help to
> > set it up and get accurate metrics. It should take only a few minutes!
> >
> > The first thing we need is the HTTP URL for the upstream master branch
> > of every project on the front page -- I'll take a git:// URL if that's
> > all they have.  If you could send me the URLs for the projects you
> > contribute to, it'd be great. This has to be done only once and we'll
> > use that to automatically detect when a patch is committed upstream.
> 
> http://git.linaro.org/git/tools/powerdebug.git
> 
> http://git.linaro.org/git/tools/pm-qa.git

I've created new projects for those two. Thanks!

> 
> [ ... ]
> 
> > Similarly, if any of the patches you see there have been superseded or
> > rejected, please do mark them as such. You can do bulk changes there
> > selecting the patches and using the form at the bottom.
> >
> > Finally, although we do our best to place patches under the appropriate
> > projects, sometimes we're not able to (e.g. when patches are sent *only*
> > to patches@l.o), and in these cases they need to be moved manually. The
> > list of patches for which we couldn't find a project are at
> >
> >http://patches.linaro.org/patchwork/project/other-unknown/list/
> 
> The two projects are hosted at git.linaro.org and belongs to linaro. The 
> mailing list is linaro-dev@. If I understood correctly with this email 
> address you can't find to which project the patchset I will send for 
> powerdebug is related to, right ?

Yep, that's correct.

> 
> I sent a patchset with "powerdebug" keyword in the subject prefix. 
> Assuming you create the "powerdebug" project, will the next patchset go 
> to the right project ? Or do I have to move the patchset to the right 
> project manually using the form ?

We don't do that right now, so yes, you'll need to move them using the
form. However, I think it'd be possible to match the prefix to an
existing project when all else fails. A custom email header would be
more robust but I understand that a prefix is probably easier to use.
What do you think?

-- 
Guilherme Salgado 


signature.asc
Description: This is a digitally signed message part
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-16 Thread Guilherme Salgado 
On Thu, 2011-06-16 at 13:25 +0300, Alexandros Frantzis wrote:
> On Wed, Jun 15, 2011 at 10:26:57AM -0300, Guilherme Salgado wrote:
> > Hi folks,
> > 
> > http://patches.linaro.org/ went live yesterday and we need your help to
> > set it up and get accurate metrics. It should take only a few minutes!
> > 
> > The first thing we need is the HTTP URL for the upstream master branch
> > of every project on the front page -- I'll take a git:// URL if that's
> > all they have.  If you could send me the URLs for the projects you
> > contribute to, it'd be great. This has to be done only once and we'll
> > use that to automatically detect when a patch is committed upstream.
> > 
> > Unfortunately, in some cases the patch that is ultimately committed
> > upstream is significantly[1] different from the one we have in our
> > records, so we can't match them. In these cases we'll need to manually
> > mark them as accepted at
> > 
> >   http://patches.linaro.org/patchwork/user/
> >   (see "Patches for which you are waiting feedback")
> > 
> 
> I think that reaching this functionality from the main page should be
> more straightforward. It wasn't clear to me that logging in and
> clicking on my name would take me to such a page.

In fact you're taken to this page every time you log in, but I agree
this is not the most obvious way to get there. At the same time I'm not
sure we want to have a link to that on the frontpage shown to anonymous
users (as it only makes sense for engineers), and showing it only to
logged in users will not be of much help. Maybe it'd be enough if I
renamed the link on the top right corner to something like 'My
dashboard'?

> 
> > Similarly, if any of the patches you see there have been superseded or
> > rejected, please do mark them as such. You can do bulk changes there
> > selecting the patches and using the form at the bottom.
> > 
> > Finally, although we do our best to place patches under the appropriate
> > projects, sometimes we're not able to (e.g. when patches are sent *only*
> > to patches@l.o), and in these cases they need to be moved manually. The
> > list of patches for which we couldn't find a project are at
> > 
> >   http://patches.linaro.org/patchwork/project/other-unknown/list/
> > 
> > And there's a form at the bottom which allows them to be moved to the
> > appropriate project. If we're missing a project just let me know and
> > I'll create it.
> 
> Are these shown in each user's personal page (I don't have any unknown
> ones so I can't say)? If not, then it would be nice to add them there
> too, so that each user can easily examine and take care of their own
> submissions.

Yes, it will show up there.

-- 
Guilherme Salgado 


signature.asc
Description: This is a digitally signed message part
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-16 Thread Alexandros Frantzis 
On Wed, Jun 15, 2011 at 10:26:57AM -0300, Guilherme Salgado wrote:
> Hi folks,
> 
> http://patches.linaro.org/ went live yesterday and we need your help to
> set it up and get accurate metrics. It should take only a few minutes!
> 
> The first thing we need is the HTTP URL for the upstream master branch
> of every project on the front page -- I'll take a git:// URL if that's
> all they have.  If you could send me the URLs for the projects you
> contribute to, it'd be great. This has to be done only once and we'll
> use that to automatically detect when a patch is committed upstream.
> 
> Unfortunately, in some cases the patch that is ultimately committed
> upstream is significantly[1] different from the one we have in our
> records, so we can't match them. In these cases we'll need to manually
> mark them as accepted at
> 
>   http://patches.linaro.org/patchwork/user/
>   (see "Patches for which you are waiting feedback")
> 

I think that reaching this functionality from the main page should be
more straightforward. It wasn't clear to me that logging in and
clicking on my name would take me to such a page.

> Similarly, if any of the patches you see there have been superseded or
> rejected, please do mark them as such. You can do bulk changes there
> selecting the patches and using the form at the bottom.
> 
> Finally, although we do our best to place patches under the appropriate
> projects, sometimes we're not able to (e.g. when patches are sent *only*
> to patches@l.o), and in these cases they need to be moved manually. The
> list of patches for which we couldn't find a project are at
> 
>   http://patches.linaro.org/patchwork/project/other-unknown/list/
> 
> And there's a form at the bottom which allows them to be moved to the
> appropriate project. If we're missing a project just let me know and
> I'll create it.

Are these shown in each user's personal page (I don't have any unknown
ones so I can't say)? If not, then it would be nice to add them there
too, so that each user can easily examine and take care of their own
submissions.

Thanks,
Alexandros

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-15 Thread Ulrich Weigand 
Guilherme Salgado  wrote:
> Is there a mailing list to which valgrind patches are sent?  If we have
> one whenever you send a patch to that list with patches@l.o CCed we'll
> be able to detect it's a valgrind patch and move it to the correct
> project.

No, there isn't.  Valgrind patch contributions work by attaching
the patch to a bugzilla record; Julian Seward then takes the patch
from there and commits it to the repository.

(Note that there isn't even a separate bugzilla for valgrind; they
use the KDE bugzilla at bugs.kde.org while setting the "product"
field to "valgrind".)

Since I don't expect there to be a significant number of further
Linaro contributions to valgrind, it's probably not worthwhile to
spend effort trying to automate tracking those ...


Mit freundlichen Gruessen / Best Regards

Ulrich Weigand

--
  Dr. Ulrich Weigand | Phone: +49-7031/16-3727
  STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E.
  IBM Deutschland Research & Development GmbH
  Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk
Wittkopp
  Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht
Stuttgart, HRB 243294


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-15 Thread Guilherme Salgado 
On Wed, 2011-06-15 at 16:44 +0200, Ulrich Weigand wrote:
> Guilherme Salgado  wrote:
> > And there's a form at the bottom which allows them to be moved to the
> > appropriate project. If we're missing a project just let me know and
> > I'll create it.
> 
> It looks like there's no project for valgrind; I have two patches
> accepted there ...

Is there a mailing list to which valgrind patches are sent?  If we have
one whenever you send a patch to that list with patches@l.o CCed we'll
be able to detect it's a valgrind patch and move it to the correct
project.

Cheers,

> 
> Mit freundlichen Gruessen / Best Regards
> 
> Ulrich Weigand
> 
> --
>   Dr. Ulrich Weigand | Phone: +49-7031/16-3727
>   STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E.
>   IBM Deutschland Research & Development GmbH
>   Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk
> Wittkopp
>   Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht
> Stuttgart, HRB 243294
> 

-- 
Guilherme Salgado 


signature.asc
Description: This is a digitally signed message part
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Re: Please help us setup patches.linaro.org

2011-06-15 Thread Ulrich Weigand 
Guilherme Salgado  wrote:
> And there's a form at the bottom which allows them to be moved to the
> appropriate project. If we're missing a project just let me know and
> I'll create it.

It looks like there's no project for valgrind; I have two patches
accepted there ...


Mit freundlichen Gruessen / Best Regards

Ulrich Weigand

--
  Dr. Ulrich Weigand | Phone: +49-7031/16-3727
  STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E.
  IBM Deutschland Research & Development GmbH
  Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk
Wittkopp
  Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht
Stuttgart, HRB 243294


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Please help us setup patches.linaro.org

2011-06-15 Thread Guilherme Salgado 
Hi folks,

http://patches.linaro.org/ went live yesterday and we need your help to
set it up and get accurate metrics. It should take only a few minutes!

The first thing we need is the HTTP URL for the upstream master branch
of every project on the front page -- I'll take a git:// URL if that's
all they have.  If you could send me the URLs for the projects you
contribute to, it'd be great. This has to be done only once and we'll
use that to automatically detect when a patch is committed upstream.

Unfortunately, in some cases the patch that is ultimately committed
upstream is significantly[1] different from the one we have in our
records, so we can't match them. In these cases we'll need to manually
mark them as accepted at

  http://patches.linaro.org/patchwork/user/
  (see "Patches for which you are waiting feedback")

Similarly, if any of the patches you see there have been superseded or
rejected, please do mark them as such. You can do bulk changes there
selecting the patches and using the form at the bottom.

Finally, although we do our best to place patches under the appropriate
projects, sometimes we're not able to (e.g. when patches are sent *only*
to patches@l.o), and in these cases they need to be moved manually. The
list of patches for which we couldn't find a project are at

  http://patches.linaro.org/patchwork/project/other-unknown/list/

And there's a form at the bottom which allows them to be moved to the
appropriate project. If we're missing a project just let me know and
I'll create it.

It'd be great if you could check the two links below at least once a
month to update the state/project of your patches. It shouldn't take
much time, but if you have any suggestions on how we can improve this,
please do let us know.

[1] If it's just slightly different but from the same author we can
still match them

-- 
Guilherme Salgado 


signature.asc
Description: This is a digitally signed message part
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev