Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: jeremy.bennett@embecosm.com
Cc: gdb-patches@sourceware.org
Subject: Re: Patch to update gdbint.texinfo [01/04]
Date: Sat, 21 Mar 2009 09:34:00 -0000	[thread overview]
Message-ID: <uhc1np750.fsf@gnu.org> (raw)
In-Reply-To: <1237202458.29424.36.camel@thomas>

> From: Jeremy Bennett <jeremy.bennett@embecosm.com>
> Date: Mon, 16 Mar 2009 11:20:58 +0000
> 
> This is the image as PDF. Diff as binary attachment.

The PDF file that was produced by Patch using these diffs came out
corrupted.  I don't know why this happened; the CR characters that I
see in the patch make me think that perhaps you produced the diffs on
a Windows machine, or maybe copied them to a Windows machine before
sending them via email.  All kinds of weird things can happen with
binary files on Windows.

It's not a good idea to send binary files as diffs, anyway.  So please
send the two binary files themselves (PDF and PNG) as binary
attachments, not the diffs against non-existing files.

By the way, I decided to put the images in the same directory as the
Texinfo files, as I don't see the need for another directory just to
hold a few files.

Thanks.


  reply	other threads:[~2009-03-21  9:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 11:21 Jeremy Bennett
2009-03-21  9:34 ` Eli Zaretskii [this message]
2009-03-21 10:30   ` Jeremy Bennett
     [not found]   ` <1237628038.3044.105.camel@thomas>
2009-03-21 12:14     ` Eli Zaretskii
2009-03-21 14:39       ` Jeremy Bennett
2009-03-21 15:58         ` Eli Zaretskii
2009-03-21 17:33         ` Joseph S. Myers
2009-03-21 18:27           ` Eli Zaretskii
2009-03-21 20:21             ` Jeremy Bennett
2009-03-22 14:24               ` Eli Zaretskii
2009-04-21 12:38             ` Joseph S. Myers
2009-04-21 18:54               ` Eli Zaretskii

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=uhc1np750.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jeremy.bennett@embecosm.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