I think we were simply being conservative when we launched our svn service years ago. Log messages are unversioned metadata, so editing them is a lossy/destructive process. We figured those facts, combined with the assumption that log messages rarely get edited, means it was best to give that power only to project owners.
I can see the argument for what you're doing -- maybe file a feature request to loosen this restriction? Of course, a workaround would be to store the backport signals in some other revision-property that you invent. (I think svn:log is special-cased to only allow owner edits.) On Mon, Mar 21, 2011 at 2:07 PM, Mike Ratcliffe <[email protected]> wrote: > I work on Firebug but have one annoyance shared by everybody else that > commits to the project. We often add things to the commit log messages > to signal that a change should be ported to a previous version e.g. > [&1.7] but I often forget to do this. > > Sadly, committers are not able to edit the log messages of their own > commits so they have to contact the project owners and ask them to > change the log message ... if a committer created the message then > surely they should have the ability to change it? > > -- > You received this message because you are subscribed to the Google Groups > "Project Hosting on Google Code" 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/google-code-hosting?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" 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/google-code-hosting?hl=en.
