Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: pgilliam@us.ibm.com
Cc: gdb-patches@sourceware.org, kevinb@redhat.com
Subject: Re: [PATCH] add 'rs6000_in_function_epilogue_p()' (Revised)
Date: Tue, 17 Jan 2006 19:29:00 -0000	[thread overview]
Message-ID: <200601171928.k0HJSqH5017519@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <200601161915.54240.pgilliam@us.ibm.com> (message from Paul 	Gilliam on Mon, 16 Jan 2006 19:15:54 -0800)

> From: Paul Gilliam <pgilliam@us.ibm.com>
> Date: Mon, 16 Jan 2006 19:15:54 -0800
> 
> --Boundary-00=_qFGzDDhs5oqznk3
> Content-Type: text/plain;
>   charset="utf-8"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> Mark,
> 
> I have made the modifications you asked for.
> 
> I would have committed the patch, but I wanted to give you a chance
> to see if my new variable name was ok: fr became curfrm.
> 
> It's still a little criptic, but I was trying to avoid making the
> condition of an 'if' statement be on two lines.

Ah, that's a good reason not too make variables and function names
overly long.  Personally I'd just named the varible "frame" (that
actually would make the function future safe, since it really should
work for any frame, and take a frame argument instead of a pc, but
that's not your fault.)

> OK to commit?

I'll leave it up to you to change curfrm into frame as suggested
above.  So, yes.  Thanks!

> I am also concerned about this:
> 
> > [ Bleah, I'd really wish people stopped sending MIME mail, especially
> >   with that stupid quoted-printable encoding.  I hate editing out all
> >   those gratuitous equal signs. ]
> > 
> 
> The mailer I am using is 'kmail'.  Here is what I get if I say 'kmail -v':
> Qt: 3.3.1
> KDE: 3.2.1
> KMail: 1.6.2

IMHO KMail is trying to emulate too many bad things from Windows mailers.

> I viewed the source of my previous message and I have to agree: Bleah!!
> 
> What mailer whould you suggest?  What mailer do you use?

Ah, well, I use emacs; it's really convenient to be able to read your
mail and edit source code from within the same application.  But
please use whatever you're comfortable with.

> In the Settings, I see I have a choice between "Allow 8-bit" or
> "MIME Compliant (Quoted Printable)".  For this message I used "Allow
> 8-bit".  I hope this does a better job.  If not, I'll have to change
> mailers.

Yes it is.  And it seems most MTA's are 8-bit clean these days.  It's
a bit sad you don't get offered the possibility to use 7-bit ASCII :(

> I thought MIME was the standard though.  Is that not the case?

Sort of.  But I think it should only used for binary attachments; not
simple text messages.

> Also, the attachment on my previous message claims to be
> "text/x-diff".  I changed this one to "text/plain".  Did that make
> any difference for you?

Yup; it's much more readable that way.

> I really appreciate your help in getting all this stuff 'right'.

Thnaks for putting up with me ;-).  I'm sure you get it more "right"
from the start next time.

Mark


  reply	other threads:[~2006-01-17 19:29 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30 23:56 [PATCH] add 'rs6000_in_function_epilogue_p()' Paul Gilliam
2005-12-01  5:21 ` Jim Blandy
2005-12-01 18:27   ` Paul Gilliam
2005-12-01 20:14     ` Paul Gilliam
2005-12-02  1:13 ` Jim Blandy
2005-12-02  1:23   ` Daniel Jacobowitz
2005-12-02 20:12     ` Paul Gilliam
2005-12-02 20:17       ` Paul Gilliam
2005-12-03  3:05       ` Jim Blandy
2005-12-02 23:38         ` Jim Blandy
2005-12-04 20:19         ` Daniel Jacobowitz
2005-12-04 18:59           ` Daniel Jacobowitz
2005-12-04 20:48           ` Jim Blandy
2005-12-04 21:12             ` Jim Blandy
2005-12-04 21:16             ` Daniel Jacobowitz
2005-12-04 21:22               ` Jim Blandy
2005-12-02  4:02   ` Joel Brobecker
2005-12-02 18:44   ` Mark Kettenis
2005-12-02 19:15   ` [PATCH] add 'rs6000_in_function_epilogue_p()' (Revised) Paul Gilliam
2005-12-02 20:28     ` Mark Kettenis
2005-12-02 21:19       ` Daniel Jacobowitz
2005-12-02 21:21         ` Mark Kettenis
2005-12-03  4:53       ` [PATCH] add 'rs6000_in_function_epilogue_p()' (Revised, again) Paul Gilliam
2005-12-03  5:43         ` Paul Gilliam
2005-12-02 21:44     ` [PATCH] add 'rs6000_in_function_epilogue_p()' (Revised) Kevin Buettner
2005-12-06 15:20       ` Paul Gilliam
2005-12-06 15:15         ` Paul Gilliam
2005-12-08  4:42         ` Kevin Buettner
2006-01-11 17:44       ` Paul Gilliam
2006-01-12  0:12         ` Paul Gilliam
2006-01-12 23:53           ` Paul Gilliam
2006-01-13 21:05             ` Mark Kettenis
2006-01-17  3:46               ` Paul Gilliam
2006-01-17 19:29                 ` Mark Kettenis [this message]
2006-02-09 17:46                 ` Kevin Buettner
2005-12-02 22:19     ` Jim Blandy
2005-12-02 22:28       ` Daniel Jacobowitz
2005-12-02 23:20         ` Jim Blandy
2005-12-03 12:48       ` Paul Gilliam

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=200601171928.k0HJSqH5017519@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=pgilliam@us.ibm.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