From: "thomas blomme" <blommethomas@gmail.com>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] blueJ
Date: Thu, 26 Oct 2006 21:49:11 +0200 [thread overview]
Message-ID: <1004fb350610261249i6edf2a78q40bec2a925861c3@mail.gmail.com> (raw)
In-Reply-To: <1004fb350610261248u701e96acx28a38f1de643c172@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
solved, yes I am a n00b ;)
2006/10/26, thomas blomme <blommethomas@gmail.com>:
>
> you mean making a bug report with filing or is that a special option I do
> not see on bugs.gentoo.org?
>
> 2006/10/26, Joshua Nichols < nichoj@gentoo.org>:
> >
> > thomas blomme wrote:
> > > what can I do to make sure it is marked stable? I would like to help
> > > but as I don't know (yet) how to write ebuild it's a bit difficult.
> > > Maybe I should learn it, is it difficult?
> >
> > You could file 'stabilization bugs' at bugs.gentoo.org . When you file
> > these, the architecture teams will go about testing the package in
> > question, and assuming nothing goes wrong, will mark it stable.
> >
> > It certainly wouldn't be a bad idea to learn about ebuilds. They are
> > basically glorified bash scripts. Details at:
> >
> > http://devmanual.gentoo.org/
> > http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml
> > http://www.gentoo.org/proj/en/java/java-devel.xml
> >
> > --
> > Joshua Nichols
> > Gentoo/Java - Project Lead
> >
> >
>
>
> --
> Van
> Thomas Blomme
--
Van
Thomas Blomme
[-- Attachment #2: Type: text/html, Size: 2379 bytes --]
prev parent reply other threads:[~2006-10-26 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 20:49 [gentoo-java] blueJ thomas blomme
2006-10-25 20:55 ` Joshua Nichols
2006-10-26 16:22 ` Fwd: " thomas blomme
[not found] ` <1004fb350610252228p7148658ie40123e03e72d6cb@mail.gmail.com>
2006-10-26 17:27 ` Joshua Nichols
2006-10-26 19:48 ` thomas blomme
2006-10-26 19:49 ` thomas blomme [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=1004fb350610261249i6edf2a78q40bec2a925861c3@mail.gmail.com \
--to=blommethomas@gmail.com \
--cc=gentoo-java@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