public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/14070] gij and -jar argument should set the manifest Class-path recursively
Date: Sat, 07 Feb 2004 23:33:00 -0000	[thread overview]
Message-ID: <20040207233341.29209.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040207231244.14070.avdyk@debian.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-02-07 23:33 -------
Confirmed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
             Status|UNCONFIRMED                 |NEW
          Component|java                        |libgcj
     Ever Confirmed|                            |1
      Known to fail|                            |3.5.0 3.3.3 3.0.4 3.3.1
                   |                            |3.2.3 3.2.2 3.4.0
   Last reconfirmed|0000-00-00 00:00:00         |2004-02-07 23:33:40
               date|                            |
            Summary|-jar argument should set the|gij and -jar argument should
                   |manifest Class-path         |set the manifest Class-path
                   |recursively                 |recursively


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14070


  parent reply	other threads:[~2004-02-07 23:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-07 23:12 [Bug java/14070] New: " avdyk at debian dot org
2004-02-07 23:25 ` [Bug java/14070] " avdyk at debian dot org
2004-02-07 23:33 ` pinskia at gcc dot gnu dot org [this message]
2004-05-06 17:14 ` [Bug libgcj/14070] gij and " pinskia at gcc dot gnu dot org
2004-10-29 10:39 ` aph at gcc dot gnu dot org
2005-01-18 12:11 ` aph at gcc dot gnu dot org
2005-04-20  2:01 ` pinskia at gcc dot gnu dot org

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=20040207233341.29209.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: link
Be 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).