From: Bjarke Istrup Pedersen <gurligebis@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-user@lists.gentoo.org
Subject: [gentoo-dev] Bugday reminder
Date: Thu, 30 Mar 2006 16:08:04 +0200 [thread overview]
Message-ID: <442BE644.8020302@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey everybody.
It's getting close and close ... is it a bird? is it a plane, no, it's
BUGDAY :-)
Hehe, and this time it's on April 1. , no, it's no april fools joke.
Something interresting has happend since last, the new bugday site has
gone into official beta, and can been seen on
http://bugday.gentoo.org/bugdaytest . Please do some testing with it,
and report any bugs you find back to me.
Best regards, and happy bug hunting.
GurliGebis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEK+ZEO+Ewtpi9rLERAhvWAKC7oO2apSJhFVit1O8DKGfJWxlTQwCgl3a+
fdlJF/tpDZCmvIz+Eo5j680=
=Wu+k
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2006-03-30 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 14:08 Bjarke Istrup Pedersen [this message]
2006-03-31 7:56 ` [gentoo-dev] Bugday reminder Kalin KOZHUHAROV
-- strict thread matches above, loose matches on Subject: below --
2006-10-06 8:36 Alexander H. Færøy
2006-09-01 15:39 [gentoo-dev] Bugday Reminder Bjarke Istrup Pedersen
2006-02-02 21:48 [gentoo-dev] Bugday reminder Bjarke Istrup Pedersen
2005-12-02 7:45 [gentoo-dev] Bugday Reminder Scott Shawcroft
2005-11-04 20:21 [gentoo-user] [gentoo-dev] Bugday reminder kloeri
2005-11-04 20:21 ` kloeri
2005-06-30 21:50 Bryan Oestergaard
2005-05-05 11:22 Bryan Oestergaard
2005-03-03 23:14 Bryan Østergaard
2004-11-04 9:56 kloeri
2003-10-01 19:09 [gentoo-dev] BugDay Reminder Brian Jackson
2003-10-01 23:42 ` Ian Leitch
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=442BE644.8020302@gentoo.org \
--to=gurligebis@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox