[2011.03-maintenance] Pull request for binutils

[2011.03-maintenance] Pull request for binutils

[Mats Kärrman]

Hello Tom,

Please pull this commit from here:

URI: git://git.openembedded.org/openembedded
Branch: org.openembedded.dev (master)

Paul Menzel (1):
      binutils-{canadian,cross}-sdk_2.18: Remove checksums and implicitly update them

Thanks,
Mats

Re: [2011.03-maintenance] Pull request for binutils

[Tom Rini]

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

On Oct 21, 2011, at 1:38 PM, Mats Kärrman wrote:

> Hello Tom,
> 
> Please pull this commit from here:
> 
> URI: git://git.openembedded.org/openembedded
> Branch: org.openembedded.dev (master)
> 
> Paul Menzel (1):
>      binutils-{canadian,cross}-sdk_2.18: Remove checksums and implicitly update them

Sorry if it wasn't clear on the wiki page but what I'm asking for is a git branch you've created somewhere (github, gitorious, whatever, is fine) and tested that you've got all of the changes you need cherry-picked in or otherwise applied.  Thanks!

- -- 
Tom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk6mIkMACgkQdZngf2G4WwNWIwCfdDRM8w8ouqgCV4h7az5a797N
dxQAnjsK4/yvXOsbAxUJoCW95GdBQaqk
=SxUa
-----END PGP SIGNATURE-----

Re: [2011.03-maintenance] Pull request for binutils

[Mats Kärrman]

Tom,
I'm sorry for the slow progress but I'm working 100% on something else so this is overtime...
What is the correct practice; to fork the oe repository at GitHub or to create a "username/maintenance" branch in the same repo?
BR // Mats
________________________________________
From: openembedded-devel-bounces@lists.openembedded.org [openembedded-devel-bounces@lists.openembedded.org] on behalf of Tom Rini [tom.rini@gmail.com]
Sent: Tuesday, October 25, 2011 4:43 AM
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [2011.03-maintenance] Pull request for binutils

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

On Oct 21, 2011, at 1:38 PM, Mats Kärrman wrote:

> Hello Tom,
>
> Please pull this commit from here:
>
> URI: git://git.openembedded.org/openembedded
> Branch: org.openembedded.dev (master)
>
> Paul Menzel (1):
>      binutils-{canadian,cross}-sdk_2.18: Remove checksums and implicitly update them

Sorry if it wasn't clear on the wiki page but what I'm asking for is a git branch you've created somewhere (github, gitorious, whatever, is fine) and tested that you've got all of the changes you need cherry-picked in or otherwise applied.  Thanks!

- --
Tom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk6mIkMACgkQdZngf2G4WwNWIwCfdDRM8w8ouqgCV4h7az5a797N
dxQAnjsK4/yvXOsbAxUJoCW95GdBQaqk
=SxUa
-----END PGP SIGNATURE-----

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [2011.03-maintenance] Pull request for binutils

[Anders Darander]

* Mats Kärrman <Mats.Karrman@tritech.se> [111025 09:37]:
> I'm sorry for the slow progress but I'm working 100% on something else
> so this is overtime...

Unfortunately a too common situation...

> What is the correct practice; to fork the oe repository at GitHub or
> to create a "username/maintenance" branch in the same repo?

Well, unless you already have a git account, with rw permission
openembedded.org (and thus can push to e.g. openembedded), the easiest
thing should be to use another hosting. I'm using github for my
pull-requests to meta-oe and oe-core.

If you do that, just:
1) fork openembedded on github
2) add the remote to you local git-tree
3) push your local branch to github, using i.e. `git push github
featureXXX`, assuming that you named the remote github.

Cheers,
Anders

-- 
Anders Darander
ChargeStorm AB / eStorm AB

Re: [2011.03-maintenance] Pull request for binutils

[Denys Dmytriyenko]

On Tue, Oct 25, 2011 at 09:50:30AM +0200, Anders Darander wrote:
> * Mats K?rrman <Mats.Karrman@tritech.se> [111025 09:37]:
> > I'm sorry for the slow progress but I'm working 100% on something else
> > so this is overtime...
> 
> Unfortunately a too common situation...
> 
> > What is the correct practice; to fork the oe repository at GitHub or
> > to create a "username/maintenance" branch in the same repo?
> 
> Well, unless you already have a git account, with rw permission
> openembedded.org (and thus can push to e.g. openembedded), the easiest
> thing should be to use another hosting. I'm using github for my
> pull-requests to meta-oe and oe-core.
> 
> If you do that, just:
> 1) fork openembedded on github
> 2) add the remote to you local git-tree
> 3) push your local branch to github, using i.e. `git push github
> featureXXX`, assuming that you named the remote github.

Just don't forget that you want your personal tree be at the tip of 
2011.03-maintenance branch, not the master oe.dev (which would otherwise be 
similar to what you just sent). Then you can cherry-pick the needed commit, 
push it to github and generate a pull request.

-- 
Denys

Re: [2011.03-maintenance] Pull request for binutils

[Mats Kärrman]

Thanks to all for your support!

I'm thinking that it would be great if the patch first went into master. Then I could pick both the binutils 2.18 related patches from there. So I started to look for information about how to make the patch go to master. I then discovered that the patch is already in patchwork but I fail to see how I make it go from there to being committed, considering I'm a user without repo write permission. Could someone tell me the next steps or point me to somewhere where this is described?

BR // Mats
________________________________________
From: openembedded-devel-bounces@lists.openembedded.org [openembedded-devel-bounces@lists.openembedded.org] on behalf of Denys Dmytriyenko [denis@denix.org]
Sent: Tuesday, October 25, 2011 7:43 PM
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [2011.03-maintenance] Pull request for binutils

On Tue, Oct 25, 2011 at 09:50:30AM +0200, Anders Darander wrote:
> * Mats K?rrman <Mats.Karrman@tritech.se> [111025 09:37]:
> > I'm sorry for the slow progress but I'm working 100% on something else
> > so this is overtime...
>
> Unfortunately a too common situation...
>
> > What is the correct practice; to fork the oe repository at GitHub or
> > to create a "username/maintenance" branch in the same repo?
>
> Well, unless you already have a git account, with rw permission
> openembedded.org (and thus can push to e.g. openembedded), the easiest
> thing should be to use another hosting. I'm using github for my
> pull-requests to meta-oe and oe-core.
>
> If you do that, just:
> 1) fork openembedded on github
> 2) add the remote to you local git-tree
> 3) push your local branch to github, using i.e. `git push github
> featureXXX`, assuming that you named the remote github.

Just don't forget that you want your personal tree be at the tip of
2011.03-maintenance branch, not the master oe.dev (which would otherwise be
similar to what you just sent). Then you can cherry-pick the needed commit,
push it to github and generate a pull request.

--
Denys

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [2011.03-maintenance] Pull request for binutils

[Anders Darander]

On 26 okt 2011, at 09:03, "Mats Kärrman" <Mats.Karrman@tritech.se> wrote:

> Thanks to all for your support!
> 
> I'm thinking that it would be great if the patch first went into master. Then I could pick both the binutils 2.18 related patches from there. So I started to look for information about how to make the patch go to master. I then discovered that the patch is already in patchwork but I fail to see how I make it go from there to being committed, considering I'm a user without repo write permission. Could someone tell me the next steps or point me to somewhere where this is described?

Well, if the patch has already been sent (and thus exists in the patchwork) there could be either one of a few situations:

* it's recently submitted, and no one has had any time to look into it yet.
* it could have been overlooked.
* it could have received comments that need to be addressed before it can be committed.

So you could always check to see if you can find any discussions of the patch on this list, otherwise ask the question again.

Cheers,
Anders

> BR // Mats
> ________________________________________
> From: openembedded-devel-bounces@lists.openembedded.org [openembedded-devel-bounces@lists.openembedded.org] on behalf of Denys Dmytriyenko [denis@denix.org]
> Sent: Tuesday, October 25, 2011 7:43 PM
> To: openembedded-devel@lists.openembedded.org
> Subject: Re: [oe] [2011.03-maintenance] Pull request for binutils
> 
> On Tue, Oct 25, 2011 at 09:50:30AM +0200, Anders Darander wrote:
>> * Mats K?rrman <Mats.Karrman@tritech.se> [111025 09:37]:
>>> I'm sorry for the slow progress but I'm working 100% on something else
>>> so this is overtime...
>> 
>> Unfortunately a too common situation...
>> 
>>> What is the correct practice; to fork the oe repository at GitHub or
>>> to create a "username/maintenance" branch in the same repo?
>> 
>> Well, unless you already have a git account, with rw permission
>> openembedded.org (and thus can push to e.g. openembedded), the easiest
>> thing should be to use another hosting. I'm using github for my
>> pull-requests to meta-oe and oe-core.
>> 
>> If you do that, just:
>> 1) fork openembedded on github
>> 2) add the remote to you local git-tree
>> 3) push your local branch to github, using i.e. `git push github
>> featureXXX`, assuming that you named the remote github.
> 
> Just don't forget that you want your personal tree be at the tip of
> 2011.03-maintenance branch, not the master oe.dev (which would otherwise be
> similar to what you just sent). Then you can cherry-pick the needed commit,
> push it to github and generate a pull request.
> 
> --
> Denys
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel