public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Palimaka <kensington@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Standardise the variable for including eclasses only once
Date: Tue, 08 Jul 2014 00:04:22 +1000	[thread overview]
Message-ID: <lpe9d6$os0$1@ger.gmane.org> (raw)
In-Reply-To: <21430.29481.773070.678302@a1i15.kph.uni-mainz.de>

On 07/04/2014 07:26 PM, Ulrich Mueller wrote:
> I have no strong preference for the variable's value. Is testing for
> a non-empty value sufficient? Then we should assign something simple
> (like "1"). If not, any string that is sufficiently random (like the
> one used in eutils) should be good.

I believe vapier introduced the original check and random value, so
perhaps he knows.



  parent reply	other threads:[~2014-07-07 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04  9:26 [gentoo-dev] Standardise the variable for including eclasses only once Ulrich Mueller
2014-07-04 13:14 ` Michał Górny
2014-07-05 18:08   ` Ulrich Mueller
2014-07-11  8:22     ` Ulrich Mueller
2014-07-07 14:04 ` Michael Palimaka [this message]
2014-07-07 20:35   ` [gentoo-dev] " Alec Warner

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='lpe9d6$os0$1@ger.gmane.org' \
    --to=kensington@gentoo.org \
    --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