Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Maxim Grigoriev <maxim@tensilica.com>
To: Maxim Grigoriev <maxim@tensilica.com>,
	  gdb-patches@sources.redhat.com,
	Daniel Jacobowitz <drow@false.org>
Subject: Re: Xtensa patch
Date: Thu, 15 Feb 2007 18:33:00 -0000	[thread overview]
Message-ID: <45D4A765.9070506@hq.tensilica.com> (raw)
In-Reply-To: <20070215150939.GA20672@caradoc.them.org>

Thanks much for your comments, Daniel.

Daniel Jacobowitz wrote:
> On Wed, Feb 14, 2007 at 04:18:53PM -0800, Maxim Grigoriev wrote:
>   
>> 2007-02-14  Maxim Grigoriev  <maxim2405@gmail.com>
>>     
> What about it - are you asking for approval, planning to commit it,
> etc?
I'm planning to commit it. My understanding is the Xtensa-related stuff 
does not need an approval,
if it comes from me, Does it ? I think asking people to take a look at 
any update is always a good idea.
>   I found this message a little mysterious :-)  I'm guessing these
> are fixes for building with a newer GCC.
>   
Exactly.
> I have only one comment - it might help to use a mailer which does not
> mangle patches.  Something's eaten the leading whitespace, probably
> format=flowed
Let me find out how I can fix it for the future. Most likely, this 
formatting problem came up together
with a newer complier after my desktop was upgraded to GNU/Linux FC5. 
I'm using Thunderbird.

Thanks !
-- Maxim




  reply	other threads:[~2007-02-15 18:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15  0:19 Maxim Grigoriev
2007-02-15 15:09 ` Daniel Jacobowitz
2007-02-15 18:33   ` Maxim Grigoriev [this message]
2007-02-15 18:46     ` Daniel Jacobowitz

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=45D4A765.9070506@hq.tensilica.com \
    --to=maxim@tensilica.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.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