Re: Bug#212863: new java policy: ok or not?
- To: Jan Schulz <jasc.usenet@gmx.de>, 212863@bugs.debian.org
- Cc: debian-java@lists.debian.org
- Subject: Re: Bug#212863: new java policy: ok or not?
- From: Ben Burton <bab@debian.org>
- Date: Wed, 15 Oct 2003 12:21:37 +1000
- Message-id: <[🔎] 20031015122137.B19027@digican.ms.unimelb.edu.au>
- In-reply-to: <[🔎] 20031014210052.GA18898@katzien.de>; from jasc.usenet@gmx.de on Tue, Oct 14, 2003 at 11:00:52PM +0200
- References: <20030926152204.GA7730@katzien.de> <3F747078.3070808@debian.org> <20030926184807.GA10340@katzien.de> <[🔎] 20031014210052.GA18898@katzien.de>
Hi. > There seems to be no more questions, but unfortunatelly nonone has > said something like 'do it' or 'file bugs with patches' or 'go > testing' or whatever until now. My only comment is that since sarge is purportedly so close to freeze and since this is more or less a complete policy rewrite, I think we should keep current java policy until after sarge. > I'm a little scared to go on, and ask Stefan for the temporary > inclusion of the findjava and other scripts in java-common I'm perfectly happy to have the scripts/etc in java-common/etc now, as long as they don't interfere with current behaviour and current policy. Ben. :)
Reply to:
- Follow-Ups:
- Bug#212863: new java policy: ok or not?
- From: Jan Schulz <jasc.usenet@gmx.de>
- Re: Bug#212863: new java policy: ok or not?
- From: Arnaud Vandyck <arnaud.vandyck@ulg.ac.be>
- Bug#212863: new java policy: ok or not?
- References:
- Bug#212863: new java policy: ok or not?
- From: Jan Schulz <jasc.usenet@gmx.de>
- Bug#212863: new java policy: ok or not?
- Prev by Date: Bug#212863: new java policy: ok or not?
- Next by Date: Bug#212863: new java policy: ok or not?
- Previous by thread: Bug#212863: new java policy: ok or not?
- Next by thread: Bug#212863: new java policy: ok or not?
- Index(es):