Processed: libgcj5: SocketChannel.get(ByteBuffer) returns 0 at EOF.

To: Michael Koch <konqueror@gmx.de>
Cc: Debian GCC maintainers <debian-gcc@lists.debian.org>(libgcj5 #281602)
Subject: Processed: libgcj5: SocketChannel.get(ByteBuffer) returns 0 at EOF.
From: owner@bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 23 Nov 2004 01:18:08 -0800
Message-id: <[🔎] handler.s.C.11012005136130.transcript@bugs.debian.org>
In-reply-to: <[🔎] 200411231103.00385.konqueror@gmx.de>
References: <[🔎] 200411231103.00385.konqueror@gmx.de>

Processing commands for control@bugs.debian.org:

> tags 281602 + upstream
Bug#281602: libgcj5: SocketChannel.get(ByteBuffer) returns 0 at EOF.
Tags were: upstream
Tags added: upstream

> tags 281602 + fixed-upstream
Bug#281602: libgcj5: SocketChannel.get(ByteBuffer) returns 0 at EOF.
Tags were: upstream
Tags added: fixed-upstream

> retitle 281602 [fixed in 4.0] SocketChannel.get(ByteBuffer) returns 0 at EOF.
Bug#281602: libgcj5: SocketChannel.get(ByteBuffer) returns 0 at EOF.
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Reply to:

References:
- Bug#281602: libgcj5: SocketChannel.get(ByteBuffer) returns 0 at EOF.
  - From: Michael Koch <konqueror@gmx.de>

Prev by Date: Processed: Re: Processed: unforward gcc report
Next by Date: Bug#281602: libgcj5: SocketChannel.get(ByteBuffer) returns 0 at EOF.
Previous by thread: Bug#281602: libgcj5: SocketChannel.get(ByteBuffer) returns 0 at EOF.
Next by thread: Bug#278549: More manpage problems
Index(es):
- Date
- Thread