net-dev  

Messages by Thread

• Re: RFR: 8365796: Remove QuicPacketNumbersTest.java [v3] Daniel Jeliński
• Re: RFR: 8365796: Remove QuicPacketNumbersTest.java [v2] Daniel Jeliński
  • Re: RFR: 8365796: Remove QuicPacketNumbersTest.java [v2] Daniel Fuchs
  • Re: RFR: 8365796: Remove QuicPacketNumbersTest.java [v2] Daniel Jeliński
• RFR: 8396100: HttpClient code cleanup Daniel Jeliński
  • Re: RFR: 8396100: HttpClient code cleanup Daniel Fuchs
  • Re: RFR: 8396100: HttpClient code cleanup Daniel Jeliński
  • Re: RFR: 8396100: HttpClient code cleanup Sean Mullan
  • Re: RFR: 8396100: HttpClient code cleanup Daniel Fuchs
  • Re: RFR: 8396100: HttpClient code cleanup [v2] Daniel Jeliński
  • Re: RFR: 8396100: HttpClient code cleanup [v2] Daniel Fuchs
  • Re: RFR: 8396100: HttpClient code cleanup [v2] Daniel Jeliński
  • Integrated: 8396100: HttpClient code cleanup Daniel Jeliński
  • Re: RFR: 8396100: HttpClient code cleanup Daniel Jeliński
• RFR: 8395929: Change the exception texts in SmtpClient and FtpClient to something mentioning LF/newline AND CR after JDK-8383756 Matthias Baesken
  • Re: RFR: 8395929: Change the exception texts in SmtpClient and FtpClient to something mentioning LF/newline AND CR after JDK-8383756 Arno Zeller
  • Re: RFR: 8395929: Change the exception texts in SmtpClient and FtpClient to something mentioning LF/newline AND CR after JDK-8383756 Martin Doerr
  • Re: RFR: 8395929: Change the exception texts in SmtpClient and FtpClient to something mentioning LF/newline AND CR after JDK-8383756 Daniel Fuchs
  • Re: RFR: 8395929: Change the exception texts in SmtpClient and FtpClient to something mentioning LF/newline AND CR after JDK-8383756 Matthias Baesken
  • Integrated: 8395929: Change the exception texts in SmtpClient and FtpClient to something mentioning LF/newline AND CR after JDK-8383756 Matthias Baesken
  • Re: RFR: 8395929: Change the exception texts in SmtpClient and FtpClient to something mentioning LF/newline AND CR after JDK-8383756 Matthias Baesken
• RFR: 8389366: SSLFlowDelegate writerCF is incorrectly initialized Daniel Jeliński
  • Re: RFR: 8389366: SSLFlowDelegate writerCF is incorrectly initialized Aleksey Shipilev
  • Re: RFR: 8389366: SSLFlowDelegate writerCF is incorrectly initialized Volkan Yazici
  • Re: RFR: 8389366: SSLFlowDelegate writerCF is incorrectly initialized Jaikiran Pai
  • Integrated: 8389366: SSLFlowDelegate writerCF is incorrectly initialized Daniel Jeliński
  • Re: RFR: 8389366: SSLFlowDelegate writerCF is incorrectly initialized Daniel Jeliński
• RFR: Merge 624e4263a16082fe6d217d87eb5f91ef42c2c0c0 Brent Christian
  • Re: RFR: Merge 624e4263a16082fe6d217d87eb5f91ef42c2c0c0 Phil Race
  • Re: RFR: Merge 624e4263a16082fe6d217d87eb5f91ef42c2c0c0 Mikael Vidstedt
  • Integrated: Merge 624e4263a16082fe6d217d87eb5f91ef42c2c0c0 Brent Christian
  • Re: RFR: Merge 624e4263a16082fe6d217d87eb5f91ef42c2c0c0 [v2] Brent Christian
• Integrated: 8394746: java/net/SocketOption/OptionsTest.java fails for IP_TOS on Windows - Invalid argument: setsocketopt Jaikiran Pai
• Re: RFR: 8394746: java/net/SocketOption/OptionsTest.java fails for IP_TOS on Windows - Invalid argument: setsocketopt [v6] Jaikiran Pai
  • Re: RFR: 8394746: java/net/SocketOption/OptionsTest.java fails for IP_TOS on Windows - Invalid argument: setsocketopt [v6] Alan Bateman
  • Re: RFR: 8394746: java/net/SocketOption/OptionsTest.java fails for IP_TOS on Windows - Invalid argument: setsocketopt [v6] Jaikiran Pai
• Re: RFR: 8394746: java/net/SocketOption/OptionsTest.java fails for IP_TOS on Windows - Invalid argument: setsocketopt [v5] Jaikiran Pai
  • Re: RFR: 8394746: java/net/SocketOption/OptionsTest.java fails for IP_TOS on Windows - Invalid argument: setsocketopt [v5] Alan Bateman
  • Re: RFR: 8394746: java/net/SocketOption/OptionsTest.java fails for IP_TOS on Windows - Invalid argument: setsocketopt [v5] Jaikiran Pai
• Re: RFR: 8394746: java/net/SocketOption/OptionsTest.java fails for IP_TOS on Windows - Invalid argument: setsocketopt [v4] Alan Bateman
  • Re: RFR: 8394746: java/net/SocketOption/OptionsTest.java fails for IP_TOS on Windows - Invalid argument: setsocketopt [v4] Jaikiran Pai
• RFR: 8394828: Problemlist java/net/httpclient/ConnectTimeoutTest and java/nio/channels/AsyncCloseAndInterrupt.java on macos 27 Jaikiran Pai
  • Integrated: 8394828: Problemlist java/net/httpclient/ConnectTimeoutTest and java/nio/channels/AsyncCloseAndInterrupt.java on macos 27 Jaikiran Pai
  • Re: RFR: 8394828: Problemlist java/net/httpclient/ConnectTimeoutTest and java/nio/channels/AsyncCloseAndInterrupt.java on macos 27 Daniel Fuchs
  • Re: RFR: 8394828: Problemlist java/net/httpclient/ConnectTimeoutTest and java/nio/channels/AsyncCloseAndInterrupt.java on macos 27 Jaikiran Pai
• RFR: 8394751: Improve test/jdk/java/net/SocketOption/OptionsTest.java for debuggability Jaikiran Pai
  • Re: RFR: 8394751: Improve test/jdk/java/net/SocketOption/OptionsTest.java for debuggability Volkan Yazici
  • Re: RFR: 8394751: Improve test/jdk/java/net/SocketOption/OptionsTest.java for debuggability Jaikiran Pai
  • Integrated: 8394751: Improve test/jdk/java/net/SocketOption/OptionsTest.java for debuggability Jaikiran Pai
• RFR: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) Daniel Fuchs
  • Re: RFR: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) Daniel Jeliński
  • Re: RFR: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) Daniel Fuchs
  • Re: RFR: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) Daniel Jeliński
  • Re: RFR: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) Daniel Jeliński
  • Re: RFR: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) [v2] Daniel Fuchs
  • Re: RFR: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) Daniel Fuchs
  • Re: RFR: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) [v2] Daniel Fuchs
  • Re: RFR: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) [v2] Daniel Jeliński
  • Re: RFR: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) [v3] Daniel Fuchs
  • Re: RFR: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) [v3] Daniel Jeliński
  • Integrated: 8394607: HttpClient HTTP/2: fully received response body discarded when peer closes connection before InputStream is read (regression from JDK-8317808) Daniel Fuchs
• Re: RFR: 8393426: GenShen: Remembered set scan should not keep old referents alive [v5] William Kemper
• RFR: 8394531: Remove support for SIO_LOOPBACK_FAST_PATH option on Windows Daniel Jeliński
  • Re: RFR: 8394531: Remove support for SIO_LOOPBACK_FAST_PATH option on Windows Alan Bateman
  • Integrated: 8394531: Remove support for SIO_LOOPBACK_FAST_PATH option on Windows Daniel Jeliński
  • Re: RFR: 8394531: Remove support for SIO_LOOPBACK_FAST_PATH option on Windows Daniel Jeliński
• RFR: 8394580: Binding a socket to 127.x.x.255 fails on Linux Daniel Jeliński
  • Re: RFR: 8394580: Binding a socket to 127.x.x.255 fails on Linux Jaikiran Pai
  • Re: RFR: 8394580: Binding a socket to 127.x.x.255 fails on Linux Alan Bateman
  • Re: RFR: 8394580: Binding a socket to 127.x.x.255 fails on Linux Daniel Jeliński
  • Re: RFR: 8394580: Binding a socket to 127.x.x.255 fails on Linux [v2] Daniel Jeliński
  • Re: RFR: 8394580: Binding a socket to 127.x.x.255 fails on Linux [v2] Alan Bateman
  • Re: RFR: 8394580: Binding a socket to 127.x.x.255 fails on Linux [v2] Daniel Jeliński
  • Re: RFR: 8394580: Binding a socket to 127.x.x.255 fails on Linux [v3] Daniel Jeliński
  • Re: RFR: 8394580: Binding a socket to 127.x.x.255 fails on Linux [v3] Alan Bateman
  • Re: RFR: 8394580: Binding a socket to 127.x.x.255 fails on Linux [v3] Jaikiran Pai
  • Re: RFR: 8394580: Binding a socket to 127.x.x.255 fails on Linux [v3] Daniel Jeliński
  • Integrated: 8394580: Binding a socket to 127.x.x.255 fails on Linux Daniel Jeliński
• RFR: 8394574: Clean up net_util Daniel Jeliński
  • Re: RFR: 8394574: Clean up net_util Alan Bateman
  • Re: RFR: 8394574: Clean up net_util Daniel Jeliński
  • Re: RFR: 8394574: Clean up net_util Alan Bateman
  • Re: RFR: 8394574: Clean up net_util [v2] Daniel Jeliński
  • Re: RFR: 8394574: Clean up net_util [v2] Daniel Jeliński
  • Re: RFR: 8394574: Clean up net_util [v2] Alan Bateman
  • Re: RFR: 8394574: Clean up net_util [v3] Daniel Jeliński
  • Re: RFR: 8394574: Clean up net_util [v3] Alan Bateman
  • Re: RFR: 8394574: Clean up net_util [v3] Daniel Jeliński
  • Integrated: 8394574: Clean up net_util Daniel Jeliński
• RFR: 8394564: Some sys/utsname.h inclusions are not needed any more Matthias Baesken
  • Re: RFR: 8394564: Some sys/utsname.h inclusions are not needed any more Matthias Baesken
  • Re: RFR: 8394564: Some sys/utsname.h inclusions are not needed any more Phil Race
  • Re: RFR: 8394564: Some sys/utsname.h inclusions are not needed any more Matthias Baesken
  • Re: RFR: 8394564: Some sys/utsname.h inclusions are not needed any more Phil Race
  • Re: RFR: 8394564: Some sys/utsname.h inclusions are not needed any more Matthias Baesken
  • Re: RFR: 8394564: Some sys/utsname.h inclusions are not needed any more Arno Zeller
  • Re: RFR: 8394564: Some sys/utsname.h inclusions are not needed any more Matthias Baesken
  • Integrated: 8394564: Some sys/utsname.h inclusions are not needed any more Matthias Baesken
  • Re: RFR: 8394564: Some sys/utsname.h inclusions are not needed any more Martin Doerr
• Re: [External] : HttpClient: no way to control name resolution per client Volkan Yazıcı
• RFR: 8394217: Allow poller group be configured to have no write pollers Alan Bateman
  • Re: RFR: 8394217: Allow poller group be configured to have no write pollers Daniel Jeliński
  • Integrated: 8394217: Allow poller group be configured to have no write pollers Alan Bateman
• RFR: 8394134: ResolverConfigurationImpl.c has unused macros and potential typo in returned value of loadConfig (win) Matthias Baesken
  • Re: RFR: 8394134: ResolverConfigurationImpl.c has unused macros and potential typo in returned value of loadConfig (win) Matthias Baesken
  • Re: RFR: 8394134: ResolverConfigurationImpl.c has unused macros and potential typo in returned value of loadConfig (win) Daniel Jeliński
  • Re: RFR: 8394134: ResolverConfigurationImpl.c has unused macros and potential typo in returned value of loadConfig (win) Matthias Baesken
  • Re: RFR: 8394134: ResolverConfigurationImpl.c has unused macros and potential typo in returned value of loadConfig (win) [v2] Matthias Baesken
  • Re: RFR: 8394134: ResolverConfigurationImpl.c has unused macros and potential typo in returned value of loadConfig (win) [v2] Daniel Jeliński
  • Re: RFR: 8394134: ResolverConfigurationImpl.c has unused macros and potential typo in returned value of loadConfig (win) [v3] Matthias Baesken
  • Re: RFR: 8394134: ResolverConfigurationImpl.c has unused macros and potential typo in returned value of loadConfig (win) [v3] Daniel Jeliński
  • Re: RFR: 8394134: ResolverConfigurationImpl.c has unused macros and potential typo in returned value of loadConfig (win) [v3] Matthias Baesken
  • Integrated: 8394134: ResolverConfigurationImpl.c has unused macros and potential typo in returned value of loadConfig (win) Matthias Baesken
• Re: RFR: 8387577: [s390x] TestSharedCloseJFR.java failure due to null pc [v3] Richard Reingruber
• RFR: 8394181: [aix] getMacAddress should call free on original malloced nddp pointer and not on some other pointer Matthias Baesken
  • Re: RFR: 8394181: [aix] getMacAddress should call free on original malloced nddp pointer and not on some other pointer Volkan Yazici
  • Re: RFR: 8394181: Call free in getMacAddress on original malloced nddp pointer and not on some other pointer Matthias Baesken
  • Integrated: 8394181: Call free in getMacAddress on original malloced nddp pointer and not on some other pointer Matthias Baesken
• RFR: 8393887: Icmp6SendEcho2/Icmp6SendEcho2ex reply buffer size might be too small Matthias Baesken
  • Re: RFR: 8393887: Icmp6SendEcho2/Icmp6SendEcho2ex reply buffer size might be too small Matthias Baesken
  • Re: RFR: 8393887: Icmp6SendEcho2/Icmp6SendEcho2ex reply buffer size might be too small Daniel Jeliński
  • Re: RFR: 8393887: Icmp6SendEcho2/Icmp6SendEcho2ex reply buffer size might be too small (win) Matthias Baesken
  • Integrated: 8393887: Icmp6SendEcho2/Icmp6SendEcho2ex reply buffer size might be too small (win) Matthias Baesken
• RFR: 8392344: Remove unused AI_CANONNAME hints in java.net.InetAddressImpl::lookupAllHostAddr native implementations Volkan Yazici
  • Re: RFR: 8392344: Remove unused AI_CANONNAME hints in java.net.InetAddressImpl::lookupAllHostAddr native implementations Daniel Jeliński
  • Re: RFR: 8392344: Remove unused AI_CANONNAME hints in java.net.InetAddressImpl::lookupAllHostAddr native implementations Volkan Yazici
  • Integrated: 8392344: Remove unused AI_CANONNAME hints in java.net.InetAddressImpl::lookupAllHostAddr native implementations Volkan Yazici
  • Re: RFR: 8392344: Remove unused AI_CANONNAME hints in java.net.InetAddressImpl::lookupAllHostAddr native implementations Michael McMahon
• RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address Michael McMahon
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address Daniel Fuchs
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address Daniel Fuchs
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address Michael McMahon
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v2] Daniel Fuchs
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v2] Michael McMahon
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v2] Volkan Yazici
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v2] Daniel Fuchs
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v2] Michael McMahon
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v2] Daniel Fuchs
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v2] Alan Bateman
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v2] Michael McMahon
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v2] Alan Bateman
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v2] Michael McMahon
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v3] Michael McMahon
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v4] Michael McMahon
  • Re: RFR: 8393057: Unix domain ServerSocketChannels need a special UDSocketAddress instance that means a system chosen address [v4] Daniel Fuchs
• RFR: 8393721: Reduce max SO_LINGER value for BSD Harald Eilertsen
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD David Holmes
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD Harald Eilertsen
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD [v2] Harald Eilertsen
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD [v2] Volkan Yazici
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD [v2] Harald Eilertsen
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD [v3] Harald Eilertsen
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD [v3] Harald Eilertsen
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD [v4] Harald Eilertsen
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD [v4] Volkan Yazici
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD [v4] Harald Eilertsen
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD [v4] Greg Lewis
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD [v4] Jaikiran Pai
  • Re: RFR: 8393721: Reduce max SO_LINGER value for BSD [v4] duke
  • Integrated: 8393721: Reduce max SO_LINGER value for BSD Harald Eilertsen
• RFR: 8393706: [windows] DefaultProxySelector.c loop continues after proxy_array was set to NULL Matthias Baesken
  • Re: RFR: 8393706: [windows] DefaultProxySelector.c loop continues after proxy_array was set to NULL Christoph Langer
  • Re: RFR: 8393706: [windows] DefaultProxySelector.c loop continues after proxy_array was set to NULL Matthias Baesken
  • Integrated: 8393706: [windows] DefaultProxySelector.c loop continues after proxy_array was set to NULL Matthias Baesken
  • Re: RFR: 8393706: [windows] DefaultProxySelector.c loop continues after proxy_array was set to NULL Arno Zeller
  • Re: RFR: 8393706: [windows] DefaultProxySelector.c loop continues after proxy_array was set to NULL Matthias Baesken
• Withdrawn: 8328894: HttpResponse.body() returns null with https target and failed proxy authentication duke
• RFR: 8393678: [windows] DefaultProxySelector.c leaks handle 'session' if initJavaClass fails Matthias Baesken
  • Re: RFR: 8393678: [windows] DefaultProxySelector.c leaks handle 'session' if initJavaClass fails Daniel Fuchs
  • Re: RFR: 8393678: [windows] DefaultProxySelector.c leaks handle 'session' if initJavaClass fails Matthias Baesken
  • Re: RFR: 8393678: [windows] DefaultProxySelector.c leaks handle 'session' if initJavaClass fails Daniel Fuchs
  • Re: RFR: 8393678: [windows] DefaultProxySelector.c leaks handle 'session' if initJavaClass fails [v2] Matthias Baesken
  • Re: RFR: 8393678: [windows] DefaultProxySelector.c leaks handle 'session' if initJavaClass fails [v2] Matthias Baesken
  • Re: RFR: 8393678: [windows] DefaultProxySelector.c leaks handle 'session' if initJavaClass fails [v2] Daniel Fuchs
  • Re: RFR: 8393678: [windows] DefaultProxySelector.c leaks handle 'session' if initJavaClass fails [v2] Matthias Baesken
  • Re: RFR: 8393678: [windows] DefaultProxySelector.c leaks handle 'session' if initJavaClass fails [v2] Daniel Fuchs
  • Re: RFR: 8393678: [windows] DefaultProxySelector.c leaks handle 'session' if initJavaClass fails [v2] Matthias Baesken
  • Integrated: 8393678: [windows] DefaultProxySelector.c leaks handle 'session' if initJavaClass fails Matthias Baesken
• RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract Volkan Yazici
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract Jaikiran Pai
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract Volkan Yazici
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract Jaikiran Pai
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract Jaikiran Pai
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract Jaikiran Pai
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v2] Volkan Yazici
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract Jaikiran Pai
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v2] Volkan Yazici
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v2] Volkan Yazici
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v2] Daniel Fuchs
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v2] Daniel Fuchs
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v2] Volkan Yazici
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract Jaikiran Pai
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract Volkan Yazici
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v3] Volkan Yazici
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v3] Daniel Fuchs
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v3] Daniel Fuchs
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v3] Volkan Yazici
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v4] Volkan Yazici
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v4] Daniel Fuchs
  • Re: RFR: 8393499: URI.compareTo doesn't follow Comparable.compareTo contract [v5] Volkan Yazici

• Earlier messages