From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] code sprints or focus-weeks
Date: Sat, 10 Mar 2007 18:22:27 +0100 [thread overview]
Message-ID: <esupgn$suu$1@sea.gmane.org> (raw)
In-Reply-To: <459A4C53.3090401@dominion.kabel.utwente.nl>
Koen Kooi wrote:
> Last night I had an idea on how to get 'big' things done:
>
> Code sprints!
What happened to this idea? When is the next (and I assume first) code
sprint?
prev parent reply other threads:[~2007-03-10 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 12:13 [RFC] code sprints or focus-weeks Koen Kooi
2007-01-02 13:36 ` Rolf Leggewie
2007-01-12 21:36 ` Marcin Juszkiewicz
2007-01-12 21:47 ` Koen Kooi
2007-01-12 23:16 ` Rolf Leggewie
2007-01-12 23:28 ` Rolf Leggewie
2007-01-13 20:13 ` Koen Kooi
2007-03-10 17:22 ` 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='esupgn$suu$1@sea.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.