From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stabellini <Stefano.Stabellini@eu.citrix.com>Stefano
Subject: Re: [PATCH] hg ignore libxl lex/yacc detritus
Date: Wed, 21 Jul 2010 17:59:50 +0100 [thread overview]
Message-ID: <C86CE616.1B43C%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <84053479-8cc4-497e-a70a-f4b3cf4b190b@default>
On 21/07/2010 17:42, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
>> They should be regenerated if the corresponding input files
>> (libxlu_cfg.l and libxlu_cfg.y) have changed. I think make will avoid
>> rebuilding them if they haven't. So the make lines shouldn't be
>> commented out.
>
> Hmmm... that means they get regenerated when an "hg update"
> is done that updates the input files, resulting in the
> files being found by hg diff, which appears to be
> what prompted my .hgignore patch.
Yes, tbh I'm not sure we can really rely on the mtimes of the input files
and the checked-in generated output files being correctly ordered in a fresh
checkout of our repository. I had to comment out the rules to generate our
virtual ACPI tables in tools/firmware/hvmloader/acpi when I used to have the
output of the ACPI compiler checked in (I've got rid of that now).
So, really, it may be we either need to remove the checked-in generated
files, or comment out the rules that build those generated files. Because we
can't rely on the file modification times being 'right' in a fresh checkout.
-- Keir
next prev parent reply other threads:[~2010-07-21 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 16:34 [PATCH] hg ignore libxl lex/yacc detritus Dan Magenheimer
2010-07-16 16:50 ` Keir Fraser
2010-07-21 15:26 ` Ian Jackson
2010-07-21 16:42 ` Dan Magenheimer
2010-07-21 16:59 ` Keir Fraser [this message]
2010-07-21 17:02 ` Keir Fraser
2010-07-23 15:53 ` Ian Jackson
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=C86CE616.1B43C%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.