Hi Raif,
Am Samstag, den 01.07.2006, 09:24 +1000 schrieb Raif S. Naffah:
hello Roman,
On Friday 30 June 2006 01:27, Roman Kennke wrote:
I checked in the Escher-based X peers and added some configury for
enabling it. To build the X peers you need the most recent Escher
library, to be
On Sat, Jul 01, 2006 at 10:33:10AM +0200, Roman Kennke wrote:
Hi Raif,
Am Samstag, den 01.07.2006, 09:24 +1000 schrieb Raif S. Naffah:
hello Roman,
On Friday 30 June 2006 01:27, Roman Kennke wrote:
I checked in the Escher-based X peers and added some configury for
enabling it. To
hello Michael,
On Saturday 01 July 2006 20:05, Michael Koch wrote:
On Sat, Jul 01, 2006 at 10:33:10AM +0200, Roman Kennke wrote:
Am Samstag, den 01.07.2006, 09:24 +1000 schrieb Raif S. Naffah:
On Friday 30 June 2006 01:27, Roman Kennke wrote:
I checked in the Escher-based X peers and
On Sat, Jul 01, 2006 at 08:22:46PM +1000, Raif S. Naffah wrote:
hello Michael,
On Saturday 01 July 2006 20:05, Michael Koch wrote:
On Sat, Jul 01, 2006 at 10:33:10AM +0200, Roman Kennke wrote:
Am Samstag, den 01.07.2006, 09:24 +1000 schrieb Raif S. Naffah:
On Friday 30 June 2006
This adds the missing implementation of a Thread MX bean at last.
This also removes the earlier VMThreadInfo interface, which turned
out to be unworkable for two reasons:
* The bean implementation and ThreadInfo exist in different packages,
and thus one can't construct the other from Java. There
Hi,
I added a helper method to ThreadGroup that the VM can use to
(relativelyly) efficiently resolve a thread id into a Thread object.
Regards,
Jeroen
2006-07-01 Jeroen Frijters [EMAIL PROTECTED]
* java/lang/ThreadGroup.java
(getThreadFromId, getThreadFromIdImpl): New
On Sat, 2006-07-01 at 14:57 +0200, Jeroen Frijters wrote:
Andrew John Hughes wrote:
The attached patch fixes the initialization of the thread IDs
in java.lang.Thread so that it starts at 1. 0 is not a valid
thread ID, and was rightly being thrown out by the managment stuff.
You just
This adds an example class for each of the existing management
beans in java.lang.management. They basically just list the properties
of each bean; a good way of testing your VM's support for the new features.
Changelog:
2006-07-01 Andrew John Hughes [EMAIL PROTECTED]
*
I'm going to check this patch in today. It fixes a bug found while
writing a MIDI file reader.
Can this go into the GCC 4.1 branch?
AG
2006-07-01 Anthony Green [EMAIL PROTECTED]
* javax/sound/midi/Track.java (vector, eventSet): Initialize.
--- javax/sound/midi/Track.java.~1.2.~
This patch (committed) fixes a few source formatting problems highlighted by
Checkstyle:
2006-07-01 David Gilbert [EMAIL PROTECTED]
* javax/swing/AbstractCellEditor.java: Source code formatting,
* javax/swing/AbstractSpinnerModel.java: Likewise,
*
This patch makes gconf the default backend.
The patch works adding a new configure option that let the user to
specify a default implementation (like FileBased or GConfBased ones).
If the user does not provides this option, than the preference backend
is FileBased (current default).
Only if the
I'm checking this trivial fix in...
2006-07-01 Anthony Green [EMAIL PROTECTED]
* javax/sound/midi/SysexMessage.java (setMessage): Fix sysex
status byte test.
--- javax/sound/midi/SysexMessage.java.~1.2.~ 2006-03-15 17:46:57.0
-0800
+++
This is the same bug in a different location. I'm going to fold my last
two ChangeLog entries together...
2006-07-01 Anthony Green [EMAIL PROTECTED]
* javax/sound/midi/SysexMessage.java (setMessage): Fix sysex
status byte test.
(setMessage): Fix it again, in a
This patch implements a MIDI file reader provider. I'm checking it in.
Thanks,
AG
2006-07-01 Anthony Green [EMAIL PROTECTED]
* resource/META-INF/services/javax.sound.midi.spi.MidiFileReader,
gnu/javax/sound/midi/file/MidiFileReader.java,
14 matches
Mail list logo