From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] push those patches, push'em up
Date: Sun, 17 Feb 2008 20:27:30 +0100 [thread overview]
Message-ID: <fpa1r2$fa6$1@ger.gmane.org> (raw)
In-Reply-To: <47B853FA.5060206@gmx.net>
Robert Schuster wrote:
> while I like the idea I wonder what we do with patches taken from other
> famous distributions.
Hi Robert,
thank you for the important question. I guess there is not one single
answer, but I think taking patches from other distributions makes a lot
of sense. That is where the proposed and optional "origin:"-line would
come into play.
Now what to do about "upstream:". I guess there are two possibilities here.
1) you can establish that the patch is already pushed upstream. Then
all you need to do is include the URL of the bug report somebody else
made. You get extra kudos for making a comment in that bug report
that OE also uses and endorses the patch. This is the most desirable
and thus you should search the upstream bug tracker first.
2) you cannot establish that the patch is already pushed upstream. I'd
say, it is best then to open a new bug report upstream, include the
URL to it in "upstream:" and let the upstream people mark it as dupe
should there have been another report. Mentioning the debian origin
should increase the likelihood of it getting applied, I assume.
I just realize now that this approach depends on debian and other
distros using public channels to push their patches upstream. Do you
happen to know if that is usually the case?
Regards
Rolf
prev parent reply other threads:[~2008-02-17 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 0:41 [RFC] push those patches, push'em up Rolf Leggewie
2008-02-13 9:59 ` Paul Sokolovsky
2008-02-13 10:31 ` Rolf Leggewie
2008-02-14 15:52 ` Leon Woestenberg
2008-02-15 17:03 ` Michael 'Mickey' Lauer
2008-02-15 18:00 ` Holger Freyther
2008-02-17 12:17 ` Rolf Leggewie
2008-02-17 15:34 ` Robert Schuster
2008-02-17 19:27 ` Rolf Leggewie [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='fpa1r2$fa6$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.