All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: [RFC] push those patches, push'em up
Date: Wed, 13 Feb 2008 01:41:02 +0100	[thread overview]
Message-ID: <foteat$i6s$1@ger.gmane.org> (raw)

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.

To get everybody on the same page and to make sure this is a sustainable
 effort, I'd also like to propose some soft policy for patches committed
to OE.  This should help us quickly find those patches still in need of
some pushing.

 1) first line in a patch starts with upstream: and goes on to list the
    URL where the bug has been reported upstream.
 2) further information can optionally be listed in the following fields
    * status: pending, accepted in XXX, rejected
    * origin: where the patch has been stolen ;-)
    * comment: any further detail such as description or reason for
               application of the patch

Comments?  Volunteers to join the cause?

Regards

Rolf




             reply	other threads:[~2008-02-13  0:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  0:41 Rolf Leggewie [this message]
2008-02-13  9:59 ` [RFC] push those patches, push'em up 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

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='foteat$i6s$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.