Skip to contentSkip to conversation

meta-oe post holiday patchwork cleanup

DISCUSSION Koen Kooi 6 participants 9 messages Jan 12, 2012 – Jan 13, 2012

lore
Share & tools
lore

Koen Kooi

author
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tl;dr version: get your subject-prefix right

Hi,

I've cleaned up patchwork by marking every meta-oe patch as archived, minus the one Martin just sent.

This means all the pending patches for meta-oe are listed here:

http://patches.openembedded.org/project/oe/list/?q=meta-oe

If your patches are missing, resend them using the method outlined in the README of the respective meta-openembedded layer.

I'll include the meta-oe one below, since too many patches still don't comply:

- ---------------------------------------------------------------------------

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: master
revision: HEAD

Send pull requests to [email protected] with '[meta-oe]' in the subject'

When sending single patches, please use something like 'git send-email -1
- --to [email protected] --subject-prefix meta-oe'

You are encouraged to fork the mirror on github
https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainer: Koen Kooi <[email protected]>

- ---------------------------------------------------------------------------

The most important thing of that is the subject prefix. I only read emails with a [meta-<foo>] subject prefix on oe-devel nowadays and I look at
http://patches.openembedded.org/project/oe/list/?q=meta- more often than oe-devel.

So: Get your subject-prefix right

And kudos to Andreas, Martin and Otavio for getting their pull requests right pretty much all the time.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk8O7MoACgkQMkyGM64RGpFPUgCfQlCodSyFbuqPSfY6PVL2cPsR YE8AoIRcwaHFCyvULMbFSH3PeFY8Fjmj
=cU1X
-----END PGP SIGNATURE-----

#1 lore raw
Quoted 10 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tl;dr version: get your subject-prefix right

Hi,

I've cleaned up patchwork by marking every meta-oe patch as archived, minus the one Martin just sent.

Quoted 6 lines

This means all the pending patches for meta-oe are listed here:

http://patches.openembedded.org/project/oe/list/?q=meta-oe

If your patches are missing, resend them using the method outlined in the README of the respective meta-openembedded layer.

I've checked mine and for some reason
http://patchwork.openembedded.org/patch/19153/
wasn't marked as Accepted by git hook (done that manually)

and [meta-oe] gpsd: disable xmlto
http://patches.openembedded.org/patch/19165/
was sent only few minutes before this email, so I guess it's still in queue.

Cheers,

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#2 lore raw
In reply to Koen Kooi
Quoted 3 lines · Koen Kooi

And kudos to Andreas, Martin and Otavio for getting their pull requests right pretty much all the time.

You're welcome :-D

Signature · 3 lines
Otavio Salvador                             O.S. Systems
E-mail: [email protected]  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
#3 lore raw
In reply to Koen Kooi
Quoted 50 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tl;dr version: get your subject-prefix right

Hi,

I've cleaned up patchwork by marking every meta-oe patch as archived, minus the one Martin just sent.

This means all the pending patches for meta-oe are listed here:

http://patches.openembedded.org/project/oe/list/?q=meta-oe

If your patches are missing, resend them using the method outlined in the README of the respective meta-openembedded layer.

I'll include the meta-oe one below, since too many patches still don't comply:

- ---------------------------------------------------------------------------

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: master
revision: HEAD

Send pull requests to [email protected] with '[meta-oe]' in the subject'

When sending single patches, please use something like 'git send-email -1
- --to [email protected] --subject-prefix meta-oe'

You are encouraged to fork the mirror on github
https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainer: Koen Kooi <[email protected]>

- ---------------------------------------------------------------------------

The most important thing of that is the subject prefix. I only read emails with a [meta-<foo>] subject prefix on oe-devel nowadays and I look at
http://patches.openembedded.org/project/oe/list/?q=meta- more often than oe-devel.

Quoted 4 lines

So: Get your subject-prefix right

And kudos to Andreas, Martin and Otavio for getting their pull requests right pretty much all the time.

While I appreciate that a blanket "throw it out; if they care they'll resend it" approach is an effective way to deal with the backlog resulting from an absence, I don't appreciate that in addition to the time I spent crafting patches to improve oe-core and submitting them (with the right prefix AFAIK), I am now expected to do so again. Further, the archived discussion of one of my patches included a request for clarification on how to address a licensing issue which was never answered, and which now presumably never will be.

This sort of practice discourages people (well, me at least) from contributing to this project.

Peter

Quoted 17 lines

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk8O7MoACgkQMkyGM64RGpFPUgCfQlCodSyFbuqPSfY6PVL2cPsR YE8AoIRcwaHFCyvULMbFSH3PeFY8Fjmj
=cU1X
-----END PGP SIGNATURE-----

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#4 lore raw
Quoted 65 lines · Peter Bigot
Quoted 50 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tl;dr version: get your subject-prefix right

Hi,

I've cleaned up patchwork by marking every meta-oe patch as archived, minus the one Martin just sent.

This means all the pending patches for meta-oe are listed here:

http://patches.openembedded.org/project/oe/list/?q=meta-oe

If your patches are missing, resend them using the method outlined in the README of the respective meta-openembedded layer.

I'll include the meta-oe one below, since too many patches still don't comply:

- ---------------------------------------------------------------------------

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: master
revision: HEAD

Send pull requests to [email protected] with '[meta-oe]' in the subject'

When sending single patches, please use something like 'git send-email -1
- --to [email protected] --subject-prefix meta-oe'

You are encouraged to fork the mirror on github
https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainer: Koen Kooi <[email protected]>

- ---------------------------------------------------------------------------

The most important thing of that is the subject prefix. I only read emails with a [meta-<foo>] subject prefix on oe-devel nowadays and I look at
http://patches.openembedded.org/project/oe/list/?q=meta- more often than oe-devel.

Quoted 4 lines

So: Get your subject-prefix right

And kudos to Andreas, Martin and Otavio for getting their pull requests right pretty much all the time.

While I appreciate that a blanket "throw it out; if they care they'll resend it" approach is an effective way to deal with the backlog resulting from an absence, I don't appreciate that in addition to the time I spent crafting patches to improve oe-core and submitting them (with the right prefix AFAIK), I am now expected to do so again. Further, the archived discussion of one of my patches included a request for clarification on how to address a licensing issue which was never answered, and which now presumably never will be.

Quoted 2 lines

This sort of practice discourages people (well, me at least) from contributing to this project.

Perhaps you can just mark them correctly in patchworks again instead of resubmitting? Somewhat easier, you can even keep a list of patch id's and do this automatically via the pwclient.

-M

#5 lore raw
Quoted 66 lines · On Thu, Jan 12, 2012 at 6:06 PM, McClintock Matthew-B29882…
Quoted 65 lines · Peter Bigot
Quoted 50 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tl;dr version: get your subject-prefix right

Hi,

I've cleaned up patchwork by marking every meta-oe patch as archived, minus the one Martin just sent.

This means all the pending patches for meta-oe are listed here:

http://patches.openembedded.org/project/oe/list/?q=meta-oe

If your patches are missing, resend them using the method outlined in the README of the respective meta-openembedded layer.

I'll include the meta-oe one below, since too many patches still don't comply:

- ---------------------------------------------------------------------------

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: master
revision: HEAD

Send pull requests to [email protected] with '[meta-oe]' in the subject'

When sending single patches, please use something like 'git send-email -1
- --to [email protected] --subject-prefix meta-oe'

You are encouraged to fork the mirror on github
https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainer: Koen Kooi <[email protected]>

- ---------------------------------------------------------------------------

The most important thing of that is the subject prefix. I only read emails with a [meta-<foo>] subject prefix on oe-devel nowadays and I look at
http://patches.openembedded.org/project/oe/list/?q=meta- more often than oe-devel.

Quoted 4 lines

So: Get your subject-prefix right

And kudos to Andreas, Martin and Otavio for getting their pull requests right pretty much all the time.

While I appreciate that a blanket "throw it out; if they care they'll resend it" approach is an effective way to deal with the backlog resulting from an absence, I don't appreciate that in addition to the time I spent crafting patches to improve oe-core and submitting them (with the right prefix AFAIK), I am now expected to do so again. Further, the archived discussion of one of my patches included a request for clarification on how to address a licensing issue which was never answered, and which now presumably never will be.

Quoted 6 lines
Quoted 2 lines

This sort of practice discourages people (well, me at least) from contributing to this project.

Perhaps you can just mark them correctly in patchworks again instead of resubmitting? Somewhat easier, you can even keep a list of patch id's and do this automatically via the pwclient.

Maybe; the only one I can see in the archive is the one that has an unanswered question. If I request a patchwork account, would I be able to do this? (I don't have/use/know anything about pwclient.)

The others don't appear to be there; maybe they got merged in since I last looked, in which case I apologize for grumbling prematurely. (My oe-core effort is unfunded so I only get a chance to poke at it for a couple days every couple weeks, and only see the emails during the off times.)

Peter

Quoted 6 lines

-M

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#6 lore raw
Quoted 3 lines · Peter Bigot

Maybe; the only one I can see in the archive is the one that has an unanswered question.  If I request a patchwork account, would I be able to do this?  (I don't have/use/know anything about pwclient.)

Not sure how the OE patchworks is setup... but I think we have made the case for getting users the ability to do that though (I know we can do this on our internal patchworks setup) ;)

-M

#7 lore raw
In reply to Peter Bigot
Quoted 71 lines · Peter Bigot
Quoted 69 lines · On Thu, Jan 12, 2012 at 6:06 PM, McClintock Matthew-B29882…
Quoted 67 lines · Peter Bigot
Quoted 50 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tl;dr version: get your subject-prefix right

Hi,

I've cleaned up patchwork by marking every meta-oe patch as archived, minus the one Martin just sent.

This means all the pending patches for meta-oe are listed here:

http://patches.openembedded.org/project/oe/list/?q=meta-oe

If your patches are missing, resend them using the method outlined in the README of the respective meta-openembedded layer.

I'll include the meta-oe one below, since too many patches still don't comply:

- ---------------------------------------------------------------------------

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: master
revision: HEAD

Send pull requests to [email protected] with '[meta-oe]' in the subject'

When sending single patches, please use something like 'git send-email -1
- --to [email protected] --subject-prefix meta-oe'

You are encouraged to fork the mirror on github
https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainer: Koen Kooi <[email protected]>

- ---------------------------------------------------------------------------

The most important thing of that is the subject prefix. I only read emails with a [meta-<foo>] subject prefix on oe-devel nowadays and I look at
http://patches.openembedded.org/project/oe/list/?q=meta- more often than oe-devel.

Quoted 4 lines

So: Get your subject-prefix right

And kudos to Andreas, Martin and Otavio for getting their pull requests right pretty much all the time.

While I appreciate that a blanket "throw it out; if they care they'll resend it" approach is an effective way to deal with the backlog resulting from an absence, I don't appreciate that in addition to the time I spent crafting patches to improve oe-core and submitting them (with the right prefix AFAIK), I am now expected to do so again. Further, the archived discussion of one of my patches included a request for clarification on how to address a licensing issue which was never answered, and which now presumably never will be.

This sort of practice discourages people (well, me at least) from contributing to this project.

Quoted 7 lines
Quoted 3 lines

Perhaps you can just mark them correctly in patchworks again instead of resubmitting? Somewhat easier, you can even keep a list of patch id's and do this automatically via the pwclient.

Maybe; the only one I can see in the archive is the one that has an unanswered question. If I request a patchwork account, would I be able to do this? (I don't have/use/know anything about pwclient.)

If it still works the same, then create patchwork account yourself with same e-mail address you're using when sending patches and you should be able to update your patches.

Quoted 5 lines

The others don't appear to be there; maybe they got merged in since I last looked, in which case I apologize for grumbling prematurely. (My oe-core effort is unfunded so I only get a chance to poke at it for a couple days every couple weeks, and only see the emails during the off times.)

Be aware that oe-core patches are not really tracked on patchwork, patchwork is used mostly for meta-* patches.

Cheers,

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#8 lore raw

2012/1/13 <[email protected]>

Quoted 92 lines · Peter Bigot
Quoted 4 lines
Quoted 2 lines · On Thu, Jan 12, 2012 at 6:06 PM, McClintock Matthew-B29882…
Quoted 1 line · Peter Bigot

On Thu, Jan 12, 2012 at 8:23 AM, Koen Kooi <

Quoted 8 lines · [email protected]> wrote:
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tl;dr version: get your subject-prefix right

Hi,

I've cleaned up patchwork by marking every meta-oe patch as

archived, minus

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

the one Martin just sent.

This means all the pending patches for meta-oe are listed here:

http://patches.openembedded.org/project/oe/list/?q=meta-oe

If your patches are missing, resend them using the method outlined

in the

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

README of the respective meta-openembedded layer.

I'll include the meta-oe one below, since too many patches still

don't comply:

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

-

---------------------------------------------------------------------------

Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: master
revision: HEAD

Send pull requests to [email protected] with '[meta-oe]' in the subject'

When sending single patches, please use something like 'git

send-email -1

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

- --to [email protected] --subject-prefix

meta-oe'

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

You are encouraged to fork the mirror on github
https://github.com/openembedded/meta-oe/ to share your patches,

this is

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

preferred for patch sets consisting of more than one patch. Other

services

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

like gitorious, repo.or.cz or self hosted setups are of course

accepted as

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

well, 'git fetch <remote>' works the same on all of them. We

recommend

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

github because it is free, easy to use, has been proven to be

reliable and

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

has a really good web GUI.

Main layer maintainer: Koen Kooi <[email protected]>

-

---------------------------------------------------------------------------

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

The most important thing of that is the subject prefix. I only read

emails

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

with a [meta-<foo>] subject prefix on oe-devel nowadays and I look at
http://patches.openembedded.org/project/oe/list/?q=meta- more often

than

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

oe-devel.

So: Get your subject-prefix right

And kudos to Andreas, Martin and Otavio for getting their pull

requests

Quoted 18 lines
Quoted 17 lines
Quoted 11 lines
Quoted 1 line

right pretty much all the time.

While I appreciate that a blanket "throw it out; if they care they'll resend it" approach is an effective way to deal with the backlog resulting from an absence, I don't appreciate that in addition to the time I spent crafting patches to improve oe-core and submitting them (with the right prefix AFAIK), I am now expected to do so again. Further, the archived discussion of one of my patches included a request for clarification on how to address a licensing issue which was never answered, and which now presumably never will be.

Quoted 2 lines

This sort of practice discourages people (well, me at least) from contributing to this project.

Perhaps you can just mark them correctly in patchworks again instead of resubmitting? Somewhat easier, you can even keep a list of patch id's and do this automatically via the pwclient.

Quoted 14 lines
Quoted 3 lines

Maybe; the only one I can see in the archive is the one that has an unanswered question. If I request a patchwork account, would I be able to do this? (I don't have/use/know anything about pwclient.)

If it still works the same, then create patchwork account yourself with same e-mail address you're using when sending patches and you should be able to update your patches.

Quoted 5 lines

The others don't appear to be there; maybe they got merged in since I last looked, in which case I apologize for grumbling prematurely. (My oe-core effort is unfunded so I only get a chance to poke at it for a couple days every couple weeks, and only see the emails during the off times.)

I could find 3 patches:
http://patches.openembedded.org/project/oe/list/?submitter=1693&state=*&archive=both

Quoted 6 lines

Be aware that oe-core patches are not really tracked on patchwork, patchwork is used mostly for meta-* patches.

oe-core patches are tracked on a different project:

http://patches.openembedded.org/project/oe-core/list/

Best regards, Frans