public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: "Joseph S. Myers" <jsm28@cam.ac.uk>, overseers@sources.redhat.com
Subject: Re: [Fwd: Cron <gdbadmin@sourceware> sh]
Date: Tue, 11 Mar 2003 16:25:00 -0000	[thread overview]
Message-ID: <3E6E0DE7.1060704@redhat.com> (raw)
In-Reply-To: <3E6A44E1.1000500@redhat.com>


> The GCC snapshot/release process uses diff -a to include diffs for binary
> files.  No users have yet complained about this causing problems with
> their version of patch, though there may not yet have been any binary
> diffs in any widely used GCC patches.

To follow this up.  Adding `-a' made GDB's mysterious diff failure go away.

Andrew


  reply	other threads:[~2003-03-11 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-08 15:00 Andrew Cagney
2003-03-08 18:25 ` Ian Lance Taylor
2003-03-08 19:11   ` Joseph S. Myers
2003-03-08 19:30     ` Andrew Cagney
2003-03-11 16:25       ` Andrew Cagney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-20  5:27 Andrew Cagney
2003-01-20 14:38 ` Christopher Faylor
2003-01-20 18:53   ` Andrew Cagney

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=3E6E0DE7.1060704@redhat.com \
    --to=ac131313@redhat.com \
    --cc=jsm28@cam.ac.uk \
    --cc=overseers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).