From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EAPI 3 and "nonfatal die"
Date: Sat, 22 Aug 2009 00:28:17 +0100 [thread overview]
Message-ID: <20090822002817.3aef6037@snowmobile> (raw)
In-Reply-To: <200908220115.22779.Arfrever@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
On Sat, 22 Aug 2009 01:15:18 +0200
Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org> wrote:
> > There was no change to the definition of nonfatal.
>
> There was a change regardless of what you think.
No, you were misreading the original wording (which I quite happy
admit was wide open for misreading), hence the need for the
clarification.
> > There was a clarification of the wording after it became clear that
> > there was room to misinterpret the intent of the original wording,
> > and it went through the usual Council-mandated process for such a
> > change.
>
> This sentence contradicts your first sentence.
No, it doesn't.
The original wording used the phrase "abort the build process due to a
failure". The intent was that this would cover commands that had
language like "Failure behaviour is EAPI dependent as per
section~\ref{sec:failure-behaviour}.".
The language for 'die' does not say "due to a failure", and so was not
supposed to be affected by 'nonfatal'.
However, that wasn't explicit, so your misreading of the intent of the
document is entirely understandable. That is why we fixed it.
> Additionally you had deceived Christian Faulhammer by not presenting
> negative consequences of your patch and your interpretation of
> original wording of definition of nonfatal().
The only consequence of the patch was to clarify what was already
stated.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-08-21 23:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 20:56 [gentoo-dev] EAPI 3 and "nonfatal die" David Leverton
2009-08-21 21:09 ` Maciej Mrozowski
2009-08-21 21:12 ` Ciaran McCreesh
2009-08-21 23:01 ` Maciej Mrozowski
2009-08-21 23:06 ` Ciaran McCreesh
2009-08-21 23:20 ` Maciej Mrozowski
2009-08-21 23:26 ` Ciaran McCreesh
2009-08-21 21:34 ` [gentoo-dev] " David Leverton
2009-08-21 22:40 ` [gentoo-dev] " Arfrever Frehtes Taifersar Arahesis
2009-08-21 22:51 ` Ciaran McCreesh
2009-08-21 23:15 ` Arfrever Frehtes Taifersar Arahesis
2009-08-21 23:28 ` Ciaran McCreesh [this message]
2009-08-21 23:39 ` Arfrever Frehtes Taifersar Arahesis
2009-08-21 23:43 ` Ciaran McCreesh
2009-08-23 2:48 ` Arfrever Frehtes Taifersar Arahesis
2009-08-23 15:19 ` Ciaran McCreesh
2009-08-22 2:46 ` [gentoo-dev] " Ryan Hill
2009-08-24 18:20 ` Christian Faulhammer
2009-08-24 19:02 ` Thomas Anderson
2009-08-25 10:21 ` Marijn Schouten (hkBst)
2009-08-25 11:35 ` Ciaran McCreesh
2009-08-24 22:09 ` Zac Medico
2009-08-24 22:16 ` Ciaran McCreesh
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=20090822002817.3aef6037@snowmobile \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-dev@lists.gentoo.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