From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Tom Tromey <tromey@redhat.com>
Cc: gcc-patches@gcc.gnu.org, classpath-patches@gnu.org
Subject: Re: [PATCH] classpath doc typos
Date: Mon, 10 Mar 2008 19:28:00 -0000 [thread overview]
Message-ID: <20080310192818.GC5539@ins.uni-bonn.de> (raw)
In-Reply-To: <m3k5kawhrh.fsf@fleche.redhat.com>
Hi Tom,
* Tom Tromey wrote on Mon, Mar 10, 2008 at 07:33:54PM CET:
> >>>>> "Ralf" == Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
>
> Ralf> Tested 'make docs info dvi pdf html' in classpath/doc. OK for trunk?
> Ralf> If yes, will somebody push this upstream into classpath for me?
>
> Yes, this is ok. Thanks. Did Dalibor put it in Classpath? If not,
> let me know, and I will do it.
I put it in GCC and Dalibor put it in classpath.
Cheers,
Ralf
next prev parent reply other threads:[~2008-03-10 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 14:20 Ralf Wildenhues
2008-03-08 13:32 ` Ralf Wildenhues
2008-03-09 16:20 ` [cp-patches] " Dalibor Topic
2008-03-10 19:25 ` Tom Tromey
2008-03-10 19:28 ` Ralf Wildenhues [this message]
2008-03-10 19:38 ` [cp-patches] " Dalibor Topic
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=20080310192818.GC5539@ins.uni-bonn.de \
--to=ralf.wildenhues@gmx.de \
--cc=classpath-patches@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tromey@redhat.com \
/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).