Julian Foad <julianfoad@btopenworld.com> writes:
> Should I leave "--revprop" as a synonym for "--rev-prop" for the
> time being? I probably should, because scripts like
> propchange-email.pl will need to be updated accordingly. (I can
> update the master copy in the source tree, but not the copy running
> on tigris.org.)
I think the only thing that would prompt them to change would be the
removal of support for the old option, but do as you think best.
> Grepping through, the other related thing is the name
> "{pre,post}-revprop-change"; should I put the extra hyphen in there
> too? Perhaps not.
>
> Or should I forget the whole idea? I've written and tested the
> patch (including keeping "--revprop" as an obolete synonym), so can
> commit easily if you're still happy with the idea.
I would be harsh to change the hook scripts' names. Then people's
repositories will start doing unexpected things, which is more serious
than clients doing unexpected things. On other hand, one hates to go
to 1.0 with a name that people don't like. So I guess we'd ideally
have code that looks first for 'pre-rev-prop-change', then for
'pre-revprop-change' if the first fails... Heh heh <evil grin>
I like the consistency and intuitiveness of "--revprop", because it
treats 'revprop' as a single compound noun. Others find this neither
consistent nor intuitive. These people are clearly out of their
heads, but I can't prove it :-).
So, paint the bikeshed any color you please.
Luv,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 28 03:04:00 2003