From: Daniel Jacobowitz <drow@false.org>
To: Mark Shinwell <shinwell@codesourcery.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] enabling gprof for cross builds
Date: Tue, 09 May 2006 01:38:00 -0000 [thread overview]
Message-ID: <20060508210709.GA18427@nevyn.them.org> (raw)
In-Reply-To: <445F9A15.7000103@codesourcery.com>
Please include a ChangeLog entry next time :-)
Otherwise, I think this is fine; as I told you earlier, I've been
meaning to do it for years.
Do you have write access to gcc yet? Changes to the top level files
need to be committed in sync to both trees.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-08 21:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 23:48 Mark Shinwell
2006-05-09 1:38 ` Daniel Jacobowitz [this message]
2006-05-09 2:05 ` Ben Elliston
2006-05-09 20:33 ` Mark Shinwell
2006-05-24 12:31 ` Mark Shinwell
2006-05-24 14:28 ` Daniel Jacobowitz
2006-05-24 17:09 ` Mark Shinwell
2007-04-09 17:46 Sanjay Chadha
2007-04-12 4:08 ` Ben Elliston
2007-04-12 15:13 ` Danny Backx
2007-04-13 1:09 ` John Tytgat
2007-04-19 21:54 ` Danny Backx
2007-04-20 14:28 ` Nick Clifton
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=20060508210709.GA18427@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
--cc=shinwell@codesourcery.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).