From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Upstreaming patches
Date: Mon, 11 Apr 2011 16:46:20 -0700 [thread overview]
Message-ID: <4DA392CC.4010401@balister.org> (raw)
Saul Wold asked me about upstreaming some of the patches in OE.
Apparently, Intel has some people who can look at submitting some of our
patches upstream.
The question is, what do we do about attribution? The problem is that is
not simple for many cases working out who created the patch. Rather than
spend time chasing through the revision history, it would be simpler to
send the patches upstream mentioning the source as derived from OE.
My thoughts are no reasonable OE contributor would object to someone
else upstreaming their patches :), but I thought I should ask people
what they thought.
Obviously, if there is a complex patch the situation is different, but I
suspect most of the easy patches do not fall into this category.
Comments?
Philip
next reply other threads:[~2011-04-11 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 23:46 Philip Balister [this message]
2011-04-11 23:59 ` Upstreaming patches Graham Gower
2011-04-12 7:32 ` Paul Menzel
2011-04-12 7:34 ` Esben Haabendal
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=4DA392CC.4010401@balister.org \
--to=philip@balister.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.