www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] Closed: (INFRA-2366) Fix old revision numbers in subversion log messages
Date Sat, 24 Apr 2010 11:23:49 GMT

     [ https://issues.apache.org/jira/browse/INFRA-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Gavin closed INFRA-2366.

    Resolution: Won't Fix

Subversion devs I've spoken to say this isnt worth doing.

> Fix old revision numbers in subversion log messages
> ---------------------------------------------------
>                 Key: INFRA-2366
>                 URL: https://issues.apache.org/jira/browse/INFRA-2366
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Senthil Kumaran
>            Priority: Minor
> The subversion project code was migrated to asf subversion repository. In the log messages
of subversion project we have references to old revision numbers (svn.collab.net) which should
be modified to refer the new revision numbers from the ASF subversion repository. 
> A discussion about the above is here - http://mail-archives.apache.org/mod_mbox/subversion-dev/200911.mbox/browser
> I ve come up with a script http://svn.apache.org/repos/asf/subversion/trunk/tools/dev/log_revnum_change_asf.py
which helps in modifying the revision numbers inside log messages. As you can see this script
changes svn:log property in the repository and will generate one email per change. I do not
want to flood commits@ mailing list with these emails, hence I want a schedule to perform
this operation, so that others are not spammed. 
> I ve estimated that this script will take approximately 30 minutes (upper bound) to run
to completion. Please let me know when this can be scheduled after disabling pre-revprop-change
hook in ASF subversion repository.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message