[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-devel] Order of the attr command parameters
From: |
Lapo Luchini |
Subject: |
[Monotone-devel] Order of the attr command parameters |
Date: |
Tue, 13 Jul 2010 09:18:26 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.8) Gecko/20100219 SeaMonkey/2.0.3 |
While using SVN at work I noticed that mtn's and svn's attribute
manipulation parameters have got two parameter inverted, that is:
svn propset PROPNAME PROPVAL PATH...
mtn attr set PATH ATTR VALUE
>From the point of view of attr=value, I think monotone's order has a
sense, but OTOH svn's order easily allows to apply the attribute to many
files; e.g.:
svn propset svn:mime-type text/css *.css
for n in *.sh; do mtn attr set $n mtn:execute true; done
I think the former is easier to use. Well, in fact nothing is really
limiting the "attr set" command to accept more PATH names one after
another: last two parameters would always be ATTR and VALUES and the
previous ones would be all PATHs. But I think it would feel a little
more strange, even though retro-compatible.
What do you think of it?
--
Lapo Luchini - http://lapo.it/
“I think, therefore I am… I think.” (Nordom, videogame "Torment", 1999)
- [Monotone-devel] Order of the attr command parameters,
Lapo Luchini <=