bzr svn propedit equivalent

[Aaron Bentley]

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

Sabin Iacob wrote:
> Aaron Bentley wrote:
>> The settings don't refer to particular files, so they're not like
>> subversion file properties.
>>   
> 
> So, while "propedit" would be fit here, as we are editing a (branch)
> property/attribute, the name could be confusing for subversion users
> accustomed to the command editing file attributes.

They're not generic properties.  They're specifically configuration values.

> Would something like "set" be better (bzr set option value)? other ideas?
> 
> I am also thinking about making the tree namespace the default, since
> .bzr/branch.conf travels with the branch when moving stuff around, while
> settings from locations.conf would have to be regenerated (or updated by
> hand). What would be the concerns? The wiki says that some options like
> post_commit are ignored due to security concerns (?), for instance.

I don't think it's helpful to call them "namespaces" because they
cascade.  And I would think you should support setting the overall
configuration values.

So I would suggest making "general" the default, and allowing users to
specify --location or --branch as options.

e.g.
"bzr set-config --branch create_signatures always"

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

iD8DBQFF6HDz0F+nu1YWqI0RAnuNAJ9MFUNqg26gG2ZGv4TxCibnx9GKxwCfehVN
RCjTYgyZFeDMzjPXZnC7XRA=
=Stqc
-----END PGP SIGNATURE-----