<div dir="ltr">On Thu, Aug 1, 2013 at 11:56 AM, Burton, Ross <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 1 August 2013 11:50, Laszlo Papp <<a href="mailto:lpapp@kde.org">lpapp@kde.org</a>> wrote:<br>
> Speaking of gerrit terms: I would prefer that you didn't submit this.<br>
><br>
> I would like it to be more specific. If it cannot be more specific, it<br>
> should provide further information to get more specific information. Note,<br>
> machine configuration can be the command line as well, so this would still<br>
> be vague.<br>
<br>
</div>It cannot be more specific without dumping the entire machine<br>
configuration, which won't help because a variable is *not* set.<br></blockquote><div><br></div><div>No no, it could print out the concrete file to look up, not just a name. Besides, I would probably even print a warning about the entry point and load address not set.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
By "machine configuration can be in the command line" do you mean<br>
MACHINE=foo? And if so, why does that mean the statement is vague?<br></blockquote><div><br></div><div>Well, you could place a warning for instance when it is set to the same as in the config file. That is probably not what the user intended.</div>
</div></div></div>