Hey,

It looks like I introduced an error into the svn commit log with r925135:
"AVRO-251" should read "AVRO-451". It looks like there's a mechanism
available to edit revision log messages (using svnadmin on the box hosting
the repository), but do we want to put a policy in place to gate such edits?

Thanks,
Jeff

On 06/01/2010 09:51 AM, Jeff Hammerbacher wrote:
> It looks like I introduced an error into the svn commit log with r925135:
> "AVRO-251" should read "AVRO-451". It looks like there's a mechanism
> available to edit revision log messages (using svnadmin on the box hosting
> the repository), but do we want to put a policy in place to gate such edits?

You don't need to log in to the server anymore.

http://subversion.apache.org/faq.html#change-log-msg

I tried this and it seemed to work.

Doug

Great, thanks. So no process around edits to the commit log? Fire at will is
fine by me.

On Tue, Jun 1, 2010 at 11:10 AM, Doug Cutting <[EMAIL PROTECTED]> wrote:

> On 06/01/2010 09:51 AM, Jeff Hammerbacher wrote:
>
>> It looks like I introduced an error into the svn commit log with r925135:
>> "AVRO-251" should read "AVRO-451". It looks like there's a mechanism
>> available to edit revision log messages (using svnadmin on the box hosting
>> the repository), but do we want to put a policy in place to gate such
>> edits?
>>
>
> You don't need to log in to the server anymore.
>
> http://subversion.apache.org/faq.html#change-log-msg
>
> I tried this and it seemed to work.
>
> Doug
>

On 06/02/2010 12:04 PM, Jeff Hammerbacher wrote:
> So no process around edits to the commit log?

The process is, when you backport a patch to a branch, update trunk's
change log too, so that it tells the truth.  In these cases, when a
patch is merged to the 1.3 branch, it will no longer first appear in
1.4.0, but in 1.3.3.

Doug