All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] push those patches, push'em up
Date: Sun, 17 Feb 2008 16:34:18 +0100	[thread overview]
Message-ID: <47B853FA.5060206@gmx.net> (raw)
In-Reply-To: <foteat$i6s$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

Hi,
while I like the idea I wonder what we do with patches taken from other
famous distributions.

E.g. I like apt-get source <package> to see which flaws the Debianistas
already found and worked-around/fixed and often just include their
patches into OE. Since the Debian team is often interested to get their
patches merged upstream, that means less work for us. :)

Regards
Robert

Rolf Leggewie schrieb:
> Hi,
> 
> OE has quite many patches that are just too valuable to keep to
> ourselves.  In the spirit of our bug sprint weekends, I want to propose
> patch-pushing weekends.  Maybe we can even replace the former with the
> latter.  I'd like to propose the coming weekend as the first of this kind.
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2008-02-17 15:35 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 [this message]
2008-02-17 19:27   ` Rolf Leggewie

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=47B853FA.5060206@gmx.net \
    --to=thebohemian@gmx.net \
    --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.