All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: bug & patch weekend
Date: Fri, 25 Jul 2008 02:43:06 +0200	[thread overview]
Message-ID: <g6b7io$kun$1@ger.gmane.org> (raw)

Hi,

how about a "bug & patch sprint" next weekend?  That is the first
weekend in August and if I am not mistaken that's when our bug squashing
used to happen.

Of course, all bug work is appreciated - at any time - but I'd like to
raise particular awareness for the following three goals

 1) get the count of bugs with open patches down
 2) get the count of bugs with new and updated bb files down
 3) push as many of our patches upstream as possible
    and mark others as OE-only

How about it?  The sun may be shining, but OE is calling ;-)

Regards

Rolf


PS: I don't assume the imminent switch to git should affect this.  If it
does, let us know.




             reply	other threads:[~2008-07-25  0:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25  0:43 Rolf Leggewie [this message]
2008-07-25 18:12 ` bug & patch weekend Michael 'Mickey' Lauer
2008-07-27 11:34   ` Leon Woestenberg
2008-07-31 17:48     ` Philippe De Swert
2008-08-02 10:41 ` Michael 'Mickey' Lauer

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='g6b7io$kun$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.