Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Pull request with misc changes
Date: Tue, 10 May 2011 22:39:51 -0700	[thread overview]
Message-ID: <4DCA2127.7090006@linux.intel.com> (raw)
In-Reply-To: <BANLkTikrvH3Z2R3u+tBFL_O=C=Cg8nqFew@mail.gmail.com>



On 05/10/2011 11:20 AM, Otavio Salvador wrote:
> On Tue, May 10, 2011 at 15:00, Saul Wold <sgw@linux.intel.com> wrote:
>> Is there a reason you can't use the oe-core-contrib repo and create a branch
>> there?  Can the script be modified to support github also?
> 
> Not a hard one but I prefer to have it into our repository since
> people can fork it there and follow it.

I use the script for multiple repositories (poky, oe-core, meta-intel,
and various other layers). A configurable remote URL would be a
reasonable thing to add to the script. Perhaps leveraging something from
the current .git/config ? I haven't really looked into it, but if
someone else wants to I am not opposed to discussing it.

--
Darren

> 
>> It creates get another remote that we need to fetch from.
> 
> Or it creates another remote I need to push to.
> 
> To merge you don't need to add a remote but pull from the git URL
> included into the pull command line.
> 
> ...
>>> On the patch itself? Any doc describing an example of it?
>>>
>> Mark Hatle has (or will have shortly) a proposal out to the OE community for
>> commit and patch message guidelines, as a starting point, you can look at
>> the wiki:
>>
>> https://wiki.yoctoproject.org/wiki/Recipe_%26_Patch_Style_Guide
> 
> I have pushed it already. It is available on the mailing list, please
> take a look.
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel



      reply	other threads:[~2011-05-11  5:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 19:15 Pull request with misc changes Otavio Salvador
2011-05-10  5:17 ` Saul Wold
2011-05-10 12:53   ` Otavio Salvador
2011-05-10 18:00     ` Saul Wold
2011-05-10 18:13       ` Martin Jansa
2011-05-10 18:33         ` Tom Rini
2011-05-10 19:03           ` Richard Purdie
2011-05-10 19:15             ` Otavio Salvador
2011-05-10 19:32               ` Richard Purdie
2011-05-10 19:36               ` Chris Larson
2011-05-10 20:24             ` Martin Jansa
2011-05-10 21:31               ` Koen Kooi
2011-05-11  9:17               ` Richard Purdie
2011-05-11 10:06                 ` Koen Kooi
2011-05-10 18:20       ` Otavio Salvador
2011-05-11  5:39         ` Darren Hart [this message]

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=4DCA2127.7090006@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox