public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tromey@gcc.gnu.org To: tromey@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: libgcj/7416 Date: Tue, 31 Dec 2002 14:56:00 -0000 [thread overview] Message-ID: <20021231225601.26343.qmail@sources.redhat.com> (raw) The following reply was made to PR libgcj/7416; it has been noted by GNATS. From: tromey@gcc.gnu.org To: gcc-gnats@gcc.gnu.org Cc: Subject: libgcj/7416 Date: 31 Dec 2002 22:49:38 -0000 CVSROOT: /cvs/gcc Module name: gcc Branch: gcc-3_3-branch Changes by: tromey@gcc.gnu.org 2002-12-31 14:49:38 Modified files: libjava : ChangeLog libjava/java/lang: System.java libjava/java/security: Security.java libjava/javax/naming: InitialContext.java Log message: Fix for PR libgcj/7416: * javax/naming/InitialContext.java (init): Use gnu.classpath.home.url. * java/security/Security.java: Use new properties. (loadProviders): Accept base url; use it. * java/lang/System.java: Document gnu.classpath.vm.shortname, and gnu.classpath.home.url. (gnu.classpath.home.url): Define. (gnu.classpath.vm.shortname): Likewise. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.1594.2.11&r2=1.1594.2.12 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/java/lang/System.java.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.10&r2=1.10.20.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/java/security/Security.java.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.10&r2=1.10.2.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/javax/naming/InitialContext.java.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.6&r2=1.6.2.1
next reply other threads:[~2002-12-31 22:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-31 14:56 tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-31 14:56 libgcj/7416 tromey
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021231225601.26343.qmail@sources.redhat.com \ --to=tromey@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).