public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] /etc/env.d help
Date: Sun, 11 Dec 2005 13:46:12 -0800	[thread overview]
Message-ID: <49bf44f10512111346u955994et9edf15515e07b0cd@mail.gmail.com> (raw)
In-Reply-To: <20051211180530.276fcd2e@krikkit.digimed.co.uk>

> > Thank you, that seems to have worked.  What's up with the naming
> > convention of those /etc/env.d/ files though?
>
> They are parsed in alphabetical order, so put your own settings in higher
> numbered files to override the lower numbered files. The rest of the name
> indicates the content.
>
>
> --
> Neil Bothwick

Perfect, thanks Neil.

- Grant

-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2005-12-11 21:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-10  4:18 [gentoo-user] /etc/env.d help Grant
2005-12-10  5:28 ` Norberto Bensa
2005-12-10  8:04   ` Grant
2005-12-10 11:29     ` Holly Bostick
2005-12-10 12:10     ` Francesco Riosa
2005-12-10  9:05 ` Catalin Trifu
2005-12-11 17:30   ` Grant
2005-12-11 18:05     ` Neil Bothwick
2005-12-11 21:46       ` Grant [this message]

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=49bf44f10512111346u955994et9edf15515e07b0cd@mail.gmail.com \
    --to=emailgrant@gmail.com \
    --cc=gentoo-user@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