[PATCH] TreeConfig should support sections

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel wrote:
>>I think it's terribly limiting to require all settings to be in one
>>section.  Anyhow, a bug is a bug.  If we're not going to support that
>>parameter, we should make it throw when it's supplied.

> At this point, I don't really care. I think we should fix it in one way
> or another.

My preference is to fix our API so that locations.conf can refer to
nested sections.  Otherwise, if we wanted to support aliases in
branch.conf or locations.conf, we would be SOL.

> I don't think we need to explicitly make 'section' deprecated, since we
> know it never worked.

Agreed.

> How does ConfigObj *represent* nested sections? As far as I can tell, it
> isn't something that INI format supports.

Right.  ConfigObj extends the INI format.  Nested sections are
represented using extra brackets:

[parent]
[[child]]
[[[grandchild]]]

More examples here:
http://www.voidspace.org.uk/python/configobj.html#the-config-file-format

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEyQpa0F+nu1YWqI0RAl6yAJwKT4AUbjLtMyR7CBhgyot/NNsxvQCfStFl
S3vtP6LBMIJWQ3ZRMSCQioY=
=CJF1
-----END PGP SIGNATURE-----