Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <teawater@gmail.com>, 	<gdb@sources.redhat.com>
Subject: RE: GDB record target 0.0.1 for GDB-6.6 release (It make GDB support Reversible Debugging)
Date: Fri, 10 Aug 2007 17:24:00 -0000	[thread overview]
Message-ID: <043201c7db73$57d7c930$2e08a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <uy7gje3l5.fsf@gnu.org>

On 10 August 2007 17:51, Eli Zaretskii wrote:

>> From: "Dave Korn" <dave.korn@artimi.com>
>> Cc: <gdb@sources.redhat.com>
>> Date: Fri, 10 Aug 2007 15:53:47 +0100
>> 
>> On 10 August 2007 15:41, Eli Zaretskii wrote:
>> 
>>> I have some comments on the patch.  (Btw, in the future, please send
>>> the patch in the body of the message as text, do not compress and
>>> attach it as a binary attachment, as that makes reviewing the patch
>>> less convenient.)
>> 
>>   Less convenient than having to manually unwrap wrapped lines before you
>> can apply it?
> 
> No one said that sending patches as regular text necessarily implies
> the lines will be wrapped.

  Well, if the sender switches off wrapping, you'll find that the patch is
easy to read but the entire body of the sender's message comes out as one long
line.

>> I find that sending as an uncompressed plaintext attachment gets
>> the best of both worlds.
> 
> I only want a single world: the one where text can be read without
> jumping through the hoops.

  As far as I know, mailers haven't made anyone "jump through hoops" to read
attachments since about 1981...


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


  reply	other threads:[~2007-08-10 17:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10  9:31 teawater
2007-08-10 14:41 ` Eli Zaretskii
2007-08-10 14:53   ` Dave Korn
2007-08-10 16:50     ` Eli Zaretskii
2007-08-10 17:24       ` Dave Korn [this message]
2007-08-11  9:37         ` Eli Zaretskii
2007-08-11 23:40           ` Dave Korn
2007-08-10 17:37       ` Paul Koning
2007-08-11  9:37         ` Eli Zaretskii
2007-08-10 14:57   ` Andreas Schwab
2007-08-11  2:15   ` teawater
2007-08-10 18:18 ` Daniel Jacobowitz
2007-08-11  2:21   ` teawater
     [not found]   ` <daef60380708101837l1fcac433paca59ef60345cd60@mail.gmail.com>
2007-08-13 11:21     ` Daniel Jacobowitz
2007-08-13  3:24 Robert Bu

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='043201c7db73$57d7c930$2e08a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=teawater@gmail.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