All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	 openembeded-devel <Openembedded-devel@lists.openembedded.org>
Subject: Upcoming Bug blitz weekend ( Feb 21 - Feb 24)
Date: Wed, 5 Feb 2014 09:21:01 -0800	[thread overview]
Message-ID: <CAMKF1srght3j6YgXJq-f+pzCnRCbWTEVuxuss5KjPthUaq+JTg@mail.gmail.com> (raw)

Hi All

I would like to invite everyone to the bug fixing weekend which is
coming in 3 weeks from Feb 21 to Feb 24

Bugs in NEW status for OE-Core & related categories:

http://tinyurl.com/pu8vlaf

All bugs/enhancements in NEW status in interesting categories:

http://tinyurl.com/pjhrpwr

Please feel free to pick any of the bugs which you are interested in
and has no owner assigned to it
or no one committed to it in comments or so. If there is a doubt
please add a comment to bug or send email to existing assignee to
coordinate your fix.

Please assign the bugs to yourself beforehand and set the status to ACCEPTED

This is a potential list but not exhaustive, you are free to pick any
bugs that are not listed here
and fix them,

I also think it will be good to utilize IRC channel during the bug
blitz weekend for communicating
to supplement emails and mailing list communications

I will send the reminders of the event as we come close to it.

Looking forward to it

-Khem


             reply	other threads:[~2014-02-05 17:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 17:21 Khem Raj [this message]
2014-02-05 17:27 ` Upcoming Bug blitz weekend ( Feb 21 - Feb 24) Paul Eggleton
2014-02-05 17:27   ` [OE-core] " Paul Eggleton
2014-02-06 16:26   ` Matthieu CRAPET
2014-02-06 16:36     ` Paul Eggleton
2014-02-12 14:18 ` Trevor Woerner
2014-02-15 21:40 ` Khem Raj

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=CAMKF1srght3j6YgXJq-f+pzCnRCbWTEVuxuss5KjPthUaq+JTg@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=Openembedded-devel@lists.openembedded.org \
    --cc=openembedded-core@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.