From: Jakub Jelinek <jakub@redhat.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Joe Buck <jbuck@synopsys.COM>,
Mark Mitchell <mark@codesourcery.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC 3.0.4 Released
Date: Fri, 22 Feb 2002 02:32:00 -0000 [thread overview]
Message-ID: <20020222105704.C533@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <Pine.LNX.4.33.0202220948511.21370-100000@kern.srcf.societies.cam.ac.uk>; from Joseph S. Myers on Fri, Feb 22, 2002 at 09:49:37AM +0000
On Fri, Feb 22, 2002 at 09:49:37AM +0000, Joseph S. Myers wrote:
> On Thu, 21 Feb 2002, Joe Buck wrote:
>
> > If the patch is ordered in such a way that diffs to derived files appear after
> > diffs to the base files, then gcc_update is not needed.
>
> I don't think GNU diff has an option to provide any sort of partial
> ordering information to get the diffs ordered that way.
Yes, but it shouldn't be too hard to write an awk or perl script which would
do the necessary postprocessing of the diff.
Jakub
next prev parent reply other threads:[~2002-02-22 10:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 16:45 Mark Mitchell
2002-02-21 16:48 ` Joe Buck
2002-02-21 17:24 ` Mark Mitchell
2002-02-21 18:12 ` Joe Buck
2002-02-21 17:21 ` Joseph S. Myers
2002-02-21 17:26 ` Mark Mitchell
2002-02-21 17:42 ` Joseph S. Myers
2002-02-21 17:50 ` Joe Buck
2002-02-21 17:56 ` Joseph S. Myers
2002-02-21 18:07 ` Joe Buck
2002-02-22 1:51 ` Joseph S. Myers
2002-02-22 2:32 ` Jakub Jelinek [this message]
2002-02-21 18:33 ` Mark Mitchell
2002-02-21 17:13 the_sage2000
2002-02-22 2:57 Toon Moene
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=20020222105704.C533@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.COM \
--cc=jsm28@cam.ac.uk \
--cc=mark@codesourcery.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).