This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Modules names and other details for new classpath bug product
- From: Tom Tromey <tromey at redhat dot com>
- To: David Daney <ddaney at avtrex dot com>
- Cc: Mark Wielaard <mark at klomp dot org>, classpath at gnu dot org, java at gcc dot gnu dot org
- Date: 14 Feb 2005 17:25:39 -0700
- Subject: Re: Modules names and other details for new classpath bug product
- References: <1108400078.1701.42.camel@localhost> <4210EDF8.8080705@avtrex.com>
- Reply-to: tromey at redhat dot com
>>>>> "David" == David Daney <ddaney@avtrex.com> writes:
David> It sounds a bit questionable to merge the bug tracking system before
David> we have a single merged code base.
Classpath and libgcj are really like different branches of a single
source base. They mostly share code, but some parts are different and
they move at different speeds -- I see the situation as being
analogous to the difference between the trunk and the gui branch.
I think having a shared bug database is basically an administrative
move, recognizing that most of these bugs are really shared. We can
manage them the way we manage bugs on any branches. There are already
a fair number of bugs in the gcc bugzilla that really are classpath
bugs... merging like this just makes it simpler to push bugs upstream,
and for classpath and gcj hackers to have a shared view of the
library's state.
Tom