All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: Paul Sherwood <paul.sherwood@codethink.co.uk>
Cc: takeshi.saito.xv@renesas.com,
	automotive-discussions@lists.linuxfoundation.org,
	yocto@yoctoproject.org
Subject: Re: How to submit patches upstream for repos at git.yoctoproject.org (eg meta-renesas)
Date: Thu, 13 Aug 2015 15:32:34 +0300	[thread overview]
Message-ID: <55CC8E62.7070102@mail.bg> (raw)
In-Reply-To: <90967689f471f5ac0cf4edca77457a8c@codethink.co.uk>

Hi Paul,

On 08/13/2015 02:21 PM, Paul Sherwood wrote:
> Hi all,
> I am not affiliated to any Yocto Project member organisation, but am
> assisting with integration at the Automotive Grade Linux project, which
> is re-using some work from upstreams at git.yoctoproject.org
>
> Recently members of the AGL community have started contributing patches
> for meta-renesas at our mirror [1]. We would like to offer this and
> future work to upstream, and I am hoping to understand so that I can
> help guide AGL's activities so that we are properly aligned. Please can
> someone guide us on the accepted way to offer these and subsequent patches?
>
> br
> Paul
>
> [1] https://gerrit.automotivelinux.org/gerrit/#/c/4047/

Haven't seen you for a quite a while after Karlsruhe, hope you're doing
fine.

Regarding the upstreaming guidelines, the usual steps apply - ask
contributors to push patches as close to the upstream project as
possible, and just then go downstream, like this (in order of
preference):

1. Upstream components
2. Yocto meta layer (which you are reusing)
3. AGL repos

Also, it would be great if your AGL maintainers can enforce appropriate
patch tracking by Upstream-status tag + description, as it will help
everyone.

Kind regards,
Nikolay


  reply	other threads:[~2015-08-13 12:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13 11:21 How to submit patches upstream for repos at git.yoctoproject.org (eg meta-renesas) Paul Sherwood
2015-08-13 12:32 ` Nikolay Dimitrov [this message]
2015-08-13 13:24   ` Paul Sherwood
2015-08-13 14:11     ` Nikolay Dimitrov
2015-08-13 14:32       ` Stephen Lawrence
2015-08-13 12:40 ` Alexander Kanavin

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=55CC8E62.7070102@mail.bg \
    --to=picmaster@mail.bg \
    --cc=automotive-discussions@lists.linuxfoundation.org \
    --cc=paul.sherwood@codethink.co.uk \
    --cc=takeshi.saito.xv@renesas.com \
    --cc=yocto@yoctoproject.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.