From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [2011.03-maintenance] Pull request for binutils
Date: Tue, 25 Oct 2011 13:43:58 -0400 [thread overview]
Message-ID: <20111025174358.GA7690@denix.org> (raw)
In-Reply-To: <20111025075030.GA17580@ad.chargestorm.se>
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
next prev parent reply other threads:[~2011-10-25 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 20:38 [2011.03-maintenance] Pull request for binutils Mats Kärrman
2011-10-25 2:43 ` Tom Rini
2011-10-25 7:37 ` Mats Kärrman
2011-10-25 7:50 ` Anders Darander
2011-10-25 17:43 ` Denys Dmytriyenko [this message]
2011-10-26 7:02 ` Mats Kärrman
2011-10-26 9:00 ` Anders Darander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111025174358.GA7690@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.