From: Jim Blandy <jimb@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Pre-parse XML target descriptions
Date: Fri, 05 Oct 2007 16:54:00 -0000 [thread overview]
Message-ID: <m3ir5llcxu.fsf@codesourcery.com> (raw)
In-Reply-To: <20071005153350.GA23583@caradoc.them.org> (Daniel Jacobowitz's message of "Fri, 5 Oct 2007 11:33:50 -0400")
Actually, the mechanism I suggested could be incorporated in any
case. The GDB build process should always check the checksums of the
XML input files against those stored in the files built from them,
simply to remind developers when they need to regenerate the C files.
It's just a good general principle for dealing with pre-generated
files.
next prev parent reply other threads:[~2007-10-05 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 15:34 Daniel Jacobowitz
2007-10-05 16:51 ` Jim Blandy
2007-10-05 16:54 ` Jim Blandy [this message]
2007-10-05 17:40 ` Daniel Jacobowitz
2007-10-05 17:52 ` Jim Blandy
2007-10-05 17:59 ` Daniel Jacobowitz
2007-10-15 19:26 ` Daniel Jacobowitz
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=m3ir5llcxu.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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