public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libgcj/7568: Runtime.exec ignores directory argument Date: Tue, 13 Aug 2002 18:01:00 -0000 [thread overview] Message-ID: <20020814001601.8505.qmail@sources.redhat.com> (raw) The following reply was made to PR libgcj/7568; it has been noted by GNATS. From: Tom Tromey <tromey@redhat.com> To: jmr@ugcs.caltech.edu Cc: gcc-gnats@gcc.gnu.org Subject: Re: libgcj/7568: Runtime.exec ignores directory argument Date: 13 Aug 2002 18:09:09 -0600 >>>>> "Jesse" == Jesse Rosenstock <jmr@ugcs.caltech.edu> writes: Jesse> Perhaps I'm missing something. If it were really this easy, it Jesse> would probably have been fixed before. No, it really is that easy. It's just that nobody has bothered to do the updates since Runtime was changed around. I think this patch is fine. I don't think there is any problem allocating memory in the child after a fork (with vfork there might be a problem, but we explicitly don't do that). I'm testing this and will check it in once it is done. I'm simultaneously putting in the PR 7570 patch. I think you've reached the limit of freebie patches :-(. After this, we'll have to get paperwork from you. Do you know about this process? (Maybe you already have the paperwork and I just don't know or have forgotten?) Thanks, Tom
next reply other threads:[~2002-08-14 0:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-13 18:01 Tom Tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-13 18:16 tromey 2002-08-10 14:46 Jesse Rosenstock 2002-08-10 14:06 Andrew Pinski 2002-08-10 13:46 jmr
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=20020814001601.8505.qmail@sources.redhat.com \ --to=tromey@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).