[MERGE] line-endings support: part 1 of 2: versioned properties

[Nicholas Allen]

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

|>
|> I may want to give a list of file names to set the properties on and 
not just one file. All bzr commands have the file names at the end so 
this would make sense to me and would be consistent with the other bzr 
commands. Then I can do:
|>
|> bzr prop-set prop-name prop-value file1 file2 file2 pattern1 pattern2 etc
|
| May be. But I'm not in favour of this.
Can you explain why?

Also I think the property name and value as first two arguments makes 
more sense from the user's point of view because the command changes a 
property and so the property name and value are the most important part. 
Perhaps the notation name=value would also be better rather than having 
a space (it is easier to see what you mean and would catch error when 
you don't do this). e.g:

bzr prop-set name=value file1 file2 file3....

For me this is the clearest and most logical syntax but I understand 
that this is a matter of taste/opinion and others may disagree. Another 
nice thing about this syntax is you could set multiple properties with 
one command:

bzr prop-set name1=value1 name2=value2 file1 file2 file3....

I like the equals sign because it makes it very clear what is a property 
name and what is a value on the command line and these cannot be 
confused with file names either.

Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFIA2qCbpmWsXfOU58RAt6JAJ9MNg1bSac0sE8WmCuG4d0zc0AwuwCgqeal
GvfzkcymCTP7QUx9jwlHXDk=
=IL2j
-----END PGP SIGNATURE-----