[oe] [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 at lists.openembedded.org [openembedded-devel-bounces at lists.openembedded.org] on behalf of Denys Dmytriyenko [denis at denix.org]
Sent: Tuesday, October 25, 2011 7:43 PM
To: openembedded-devel at 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 at 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 at lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel