From: Gavin Sinclair <gsinclair@...>
Date: 2012-03-10T13:20:43+09:00
Subject: Re: Configuration Convention

--0023544708e4fb37b604badbd42b
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Mar 6, 2012 at 2:14 PM, Intransition <transfire@gmail.com> wrote:

> While there are obviously some files that will always remain (e.g. .git),
> I wonder if it is possible for a convention to ever develop to mitigate all
> this. Most likely that would be in the form of a common directory to hold
> all these files, although conceivably, it could be in the form of a couple
> of shared files --one for Ruby code and one for YAML.
>

I agree.  It's insane not to have all configuration files in a "config"
directory.  But you can understand how it's evolved, and sadly it's not
going to change.

Gavin

--0023544708e4fb37b604badbd42b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Tue, Mar 6, 2012 at 2:14 PM, Intransition <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:transfire@gmail.com">transfire@gmail.c=
om</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div>While there are obviously some files that will always remain (e.g. .gi=
t), I wonder if it is possible for a convention to ever develop to mitigate=
 all this. Most likely that would be in the form of a common directory to h=
old all these files, although conceivably, it could be in the form of a cou=
ple of shared files --one for Ruby code and one for YAML.</div>

<div></div></blockquote></div><br><div>I agree. =A0It&#39;s insane not to h=
ave all configuration files in a &quot;config&quot; directory. =A0But you c=
an understand how it&#39;s evolved, and sadly it&#39;s not going to change.=
</div>

<div><br></div><div>Gavin</div>

--0023544708e4fb37b604badbd42b--