On 4/25/07, Manuzhai <[EMAIL PROTECTED]> wrote: > Well, that depends on your developers. See, the subversion command > line tool uses -rX in many places, so for anyone working with the > command line client it's kind of a natural way of specifying the > revision.
Well, I normally would agree, but from my own experience even our developers didn't follow this convention. They initially wrote "revision 123", so it's obviously not the most natural syntax. After I told them to use "r123" some of them started using that, but still not everyone. Also, not only developers are using Trac. Well, maybe the bug reporters at teo are all developers and everyone knows the syntax, but in other projects there are a lot of non-developers. They sometimes report something like "I found a bug in revision 123 and it didn't exist in revision 122." > So, I'm guessing all of your developers just use TortoiseSVN or > something. Since I'd like the Trac core to be both lightweight and > built on top of *conventions*, I think this thing you're proposing is > just fine as a plugin. What's your problem with it being a plugin? I just want to make the syntax natural for everyone. Otherwise some people will use the plugin and others won't. You will never have consistent behavior anywhere. Well, anyway, I think the plugin requires to use a space after "rev", but we have lots of "rev123" references, so it would be nice if that could be recognized, too. Thanks! Bye, Waldemar Kornewald --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
