Geir,
Two things:
1)
We forgot one more JIRA bug report --- 192. Please also close 192.
Sorry for not catching this earlier
2)
The current path sorta, kinda looks like I continue filing new JIRA
bug reports as I make progress on gnuclasspath. I don't have svn
checkin permission.
Weldon
Weldon Washburn wrote:
Geir,
Two things:
1)
We forgot one more JIRA bug report --- 192. Please also close 192.
Sorry for not catching this earlier
Is there code there that needs to come into SVN.
2)
The current path sorta, kinda looks like I continue filing new JIRA
bug reports as I
On 5/3/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
Weldon Washburn wrote:
Geir,
Two things:
1)
We forgot one more JIRA bug report --- 192. Please also close 192.
Sorry for not catching this earlier
Is there code there that needs to come into SVN.
It looks like Archie took the
Geir Magnusson Jr wrote:
We have 9 votes in favor, none against, and one reasonable question
about destination.
I think that we should let Archie bring it into SVN. :) It was
suggested as
enhanced/gnuclasspathadapter/trunk/
but I'd suggest
Tim Ellison wrote:
Geir Magnusson Jr wrote:
We have 9 votes in favor, none against, and one reasonable question
about destination.
I think that we should let Archie bring it into SVN. :) It was
suggested as
enhanced/gnuclasspathadapter/trunk/
but I'd suggest
Tim Ellison wrote:
I'm confused, we voted on HARMONY-114 and committed HARMONY-318? If
nothing else that is not very traceable.
Does the BCC that applies to HARMONY-114 also apply to -318?
Excellent catch. (Many eyes...) Also, the JIRA status were not changed
either.
I guess there's
Geir Magnusson Jr wrote:
Tim Ellison wrote:
I'm confused, we voted on HARMONY-114 and committed HARMONY-318? If
nothing else that is not very traceable.
Does the BCC that applies to HARMONY-114 also apply to -318?
Excellent catch. (Many eyes...) Also, the JIRA status were not
Sorry. Its all my fault. I was distracted by the JIRA user interface
and entered a new bug report (318) when I should have updated my old
bug report (114). All my updates are posted to 318.
Would it help if I closed 114? Or put a note that follow-on is
actually posted to 318?
On 5/2/06, Tim
Geir Magnusson Jr wrote:
We have 9 votes in favor, none against, and one reasonable question
about destination.
I think that we should let Archie bring it into SVN. :) It was
suggested as
enhanced/gnuclasspathadapter/trunk/
but I'd suggest
Archie,
Thanks for getting this entered into SVN so quickly. I did a quick
check and it looks like you grabbed the most recent version. By the
way, the directory structure is still somewhat ambiguous. I keep
thinking we may want to put .../gnu.../... in the tree to distinguish
this specific
Weldon Washburn wrote:
Thanks for getting this entered into SVN so quickly. I did a quick
check and it looks like you grabbed the most recent version. By the
way, the directory structure is still somewhat ambiguous. I keep
thinking we may want to put .../gnu.../... in the tree to distinguish
Archie Cobbs wrote:
Weldon Washburn wrote:
Thanks for getting this entered into SVN so quickly. I did a quick
check and it looks like you grabbed the most recent version. By the
way, the directory structure is still somewhat ambiguous. I keep
thinking we may want to put .../gnu.../... in
Geir Magnusson Jr wrote:
I agree. How about classlibadapter/trunk - adapter/gnu/trunk?
I'd keep it specific to classlib yet simple and mimic the classlib
structure with
classlibadapter/trunk/module/gnu
or something.
OK... although I'm not sure what purpose the module part serves.
We
Archie Cobbs wrote:
Classpath? The assumption here is that you don't need to have GNU
Classpath, right?
Argh, my apologies, for some reason I was thinking completely backwards.
Ignore most of what I said :-)
OK now I remember why I thought that before: if you're going to be using
JVM X
14 matches
Mail list logo
