From: Joshua Nichols <nichoj@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] Re: Bugs submission
Date: Tue, 28 Mar 2006 18:02:48 -0500 [thread overview]
Message-ID: <4429C098.5020708@gentoo.org> (raw)
In-Reply-To: <loom.20060329T004503-225@post.gmane.org>
Wiktor Wandachowicz wrote:
> Miroslav Šulc <miroslav.sulc@...> writes:
>
>
>> Hi,
>>
>> where should we submit bugs related to migration overlay? Should we use
>> bugs.gentoo.org?
>>
>>
>
> I'm afraid that the b.g.o maintainers wouldn't like it much...
> Maybe there should be some thread / page in the javaexperimental trac?
> (and I don't think that posting it here is best, I was corrected once)
>
> But on the other hand, some METABUG in b.g.o shouldn't be a problem,
> like the jdk-1.5 METABUG maybe? And the maintainers should know about it
> beforehand, so they wouldn't dismiss such reports as INVALID or WONTFIX.
>
>
>
I actually don't think using bugs.gentoo.org would be too bad. Although,
it would be preferred if bugs directly to java@gentoo.org, so we don't
drive bug-wranglers crazy. To this end, I made a 'bookmarkable template'
and setup a tinyurl for it:
*http://tinyurl.com/ofzha*
Please use this for reporting migration-related bugs. It should be
preset to be assigned to java@gentoo.org, block the migration bug, and
will have [migration-overlay] in the title.
Regards,
Josh
--
gentoo-java@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-28 23:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 11:06 [gentoo-java] Bugs submission Miroslav Šulc
2006-03-28 22:54 ` [gentoo-java] " Wiktor Wandachowicz
2006-03-28 23:02 ` Joshua Nichols [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 7:41 Vincent Schut
2006-04-03 16:30 ` Joshua Nichols
2006-04-04 11:29 ` Vincent Schut
2006-04-12 22:46 ` Joshua Nichols
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=4429C098.5020708@gentoo.org \
--to=nichoj@gentoo.org \
--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