From: "Bryan Ãstergaard" <kloeri@gentoo.org>
To: Joshua Nichols <nichoj@gentoo.org>
Cc: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] Gentoo Bugday and Java
Date: Fri, 30 Jun 2006 16:14:28 +0000 [thread overview]
Message-ID: <20060630161428.GA28946@woodpecker.gentoo.org> (raw)
In-Reply-To: <44A54756.6090900@gentoo.org>
On Fri, Jun 30, 2006 at 11:46:30AM -0400, Joshua Nichols wrote:
> Hey folks,
>
> Tomorrow (July 1st) is a bugday. For those who aren't familar with the
> concept, basically it's a day folks come together to squash lots and
> lots of bugs :)
>
> With the new Java system to be unmasked very soon (as in today or
> tomorrow), I hope to get back into the bug squashing swing of things for
> Java. So, if that's something peeps would like to help out with that,
> please swing by #gentoo-java and #gentoo-bugday tomorrow.
>
> [1] http://bugday.gentoo.org/
>
Small correction - the Bugday channel is #gentoo-bugs but #gentoo-bugday
is set up to forward to the right channel so nobody should be getting
lost :)
Regards,
Bryan Østergaard
--
gentoo-java@gentoo.org mailing list
prev parent reply other threads:[~2006-06-30 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 15:46 [gentoo-java] Gentoo Bugday and Java Joshua Nichols
2006-06-30 16:14 ` Bryan Ãstergaard [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=20060630161428.GA28946@woodpecker.gentoo.org \
--to=kloeri@gentoo.org \
--cc=gentoo-java@lists.gentoo.org \
--cc=nichoj@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