From: Christian Groessler <chris@groessler.org>
To: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
Cc: DJ Delorie <dj@redhat.com>, <binutils@sources.redhat.com>,
<bonzini@gnu.org>
Subject: Re: [PATCH]: missing trailing slash in toplevel makefile
Date: Wed, 17 Aug 2005 15:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0508171752590.536-100000@ds9.groessler.org> (raw)
In-Reply-To: <4302E38C.2000609@lu.unisi.ch>
Hi,
On Wed, 17 Aug 2005, Paolo Bonzini wrote:
>
> >I can apply it in src, but I don't have write access to gcc. Can someone
> >else apply it in gcc?
> >
> >
> I'll take care of that.
Thanks. I've installed the patch in src.
regards,
chris
next prev parent reply other threads:[~2005-08-17 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 20:23 Christian Groessler
2005-08-15 21:25 ` DJ Delorie
2005-08-16 20:47 ` Christian Groessler
2005-08-17 7:13 ` Paolo Bonzini
2005-08-17 15:54 ` Christian Groessler [this message]
2005-08-15 22:26 ` Hans-Peter Nilsson
2005-08-16 13:21 ` Christian Groessler
2005-08-16 13:29 ` Paolo Bonzini
2005-08-16 20:45 ` Christian Groessler
2005-08-16 14:23 ` Hans-Peter Nilsson
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=Pine.LNX.4.30.0508171752590.536-100000@ds9.groessler.org \
--to=chris@groessler.org \
--cc=binutils@sources.redhat.com \
--cc=bonzini@gnu.org \
--cc=dj@redhat.com \
--cc=paolo.bonzini@lu.unisi.ch \
/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).