You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Brett Porter (JIRA)" <ji...@apache.org> on 2010/08/20 10:10:15 UTC
[jira] Created: (INFRA-2941) import NPanday revisions into
incubator
import NPanday revisions into incubator
---------------------------------------
Key: INFRA-2941
URL: https://issues.apache.org/jira/browse/INFRA-2941
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: Podling Setup
Reporter: Brett Porter
NPanday is hosted at Codeplex. As the bridge over TFS is not compatible with svnsync, to get a dump we will need to reapply the revisions to a staged repository, then dump that and import it into the test repository.
The NPanday developers would like to continue the history from the NMaven podling that it forked from. To prepare the staged repository for the above process and keep the history, we'd follow the process below.
First, create the podling location:
$ svn mkdir https://svn.apache.org/repos/asf/incubator/npanday
(take note of the revision, let's call it $REV)
$ svn cp https://svn.apache.org/repos/asf/incubator/nmaven/branches/NMAVEN_0.14@667430 https://svn.apache.org/repos/asf/incubator/npanday/trunk
On the ASF repository:
$ svnadmin dump -r$REV:HEAD asf >npanday.dump
$ svndumpfilter include incubator/npanday incubator/nmaven <npanday.dump >npanday-filtered.dump
Then to prepare staging elsewhere:
$ svnadmin create new-staged-repo
$ svn mkdir file://$PWD/new-staged-repo/incubator
$ svnadmin load new-staged-repo <npanday-filtered.dump
take note of the revision, let's call it $NEWREV
... apply codeplex revisions ...
$ svnadmin dump -r$NEWREV:HEAD new-staged-repo >npanday-staged.dump
edit dump file to remove first revision content (ie, r$NEWREV)
Back on the ASF repository:
$ svnadmin load test <npanday-staged.dump
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2941) import NPanday revisions into
incubator
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated INFRA-2941:
--------------------------------
Attachment: base.dump.bz2
base file from asf repo
> import NPanday revisions into incubator
> ---------------------------------------
>
> Key: INFRA-2941
> URL: https://issues.apache.org/jira/browse/INFRA-2941
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Brett Porter
> Attachments: base.dump.bz2
>
>
> NPanday is hosted at Codeplex. As the bridge over TFS is not compatible with svnsync, to get a dump we will need to reapply the revisions to a staged repository, then dump that and import it into the test repository.
> The NPanday developers would like to continue the history from the NMaven podling that it forked from. To prepare the staged repository for the above process and keep the history, we'd follow the process below.
> First, create the podling location:
> $ svn mkdir https://svn.apache.org/repos/asf/incubator/npanday
> (take note of the revision, let's call it $REV)
> $ svn cp https://svn.apache.org/repos/asf/incubator/nmaven/branches/NMAVEN_0.14@667430 https://svn.apache.org/repos/asf/incubator/npanday/trunk
> On the ASF repository:
> $ svnadmin dump -r$REV:HEAD asf >npanday.dump
> $ svndumpfilter include incubator/npanday incubator/nmaven <npanday.dump >npanday-filtered.dump
> Then to prepare staging elsewhere:
> $ svnadmin create new-staged-repo
> $ svn mkdir file://$PWD/new-staged-repo/incubator
> $ svnadmin load new-staged-repo <npanday-filtered.dump
> take note of the revision, let's call it $NEWREV
> ... apply codeplex revisions ...
> $ svnadmin dump -r$NEWREV:HEAD new-staged-repo >npanday-staged.dump
> edit dump file to remove first revision content (ie, r$NEWREV)
> Back on the ASF repository:
> $ svnadmin load test <npanday-staged.dump
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2941) import NPanday revisions into
incubator
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated INFRA-2941:
--------------------------------
Attachment: base.dump.bz2
> import NPanday revisions into incubator
> ---------------------------------------
>
> Key: INFRA-2941
> URL: https://issues.apache.org/jira/browse/INFRA-2941
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Brett Porter
> Assignee: Gavin
> Attachments: base.dump.bz2
>
>
> NPanday is hosted at Codeplex. As the bridge over TFS is not compatible with svnsync, to get a dump we will need to reapply the revisions to a staged repository, then dump that and import it into the test repository.
> The NPanday developers would like to continue the history from the NMaven podling that it forked from. To prepare the staged repository for the above process and keep the history, we'd follow the process below.
> First, create the podling location:
> $ svn mkdir https://svn.apache.org/repos/asf/incubator/npanday
> (take note of the revision, let's call it $REV)
> $ svn cp https://svn.apache.org/repos/asf/incubator/nmaven/branches/NMAVEN_0.14@667430 https://svn.apache.org/repos/asf/incubator/npanday/trunk
> On the ASF repository:
> $ svnadmin dump -r$REV:HEAD asf >npanday.dump
> $ svndumpfilter include incubator/npanday incubator/nmaven <npanday.dump >npanday-filtered.dump
> Then to prepare staging elsewhere:
> $ svnadmin create new-staged-repo
> $ svn mkdir file://$PWD/new-staged-repo/incubator
> $ svnadmin load new-staged-repo <npanday-filtered.dump
> take note of the revision, let's call it $NEWREV
> ... apply codeplex revisions ...
> $ svnadmin dump -r$NEWREV:HEAD new-staged-repo >npanday-staged.dump
> edit dump file to remove first revision content (ie, r$NEWREV)
> Back on the ASF repository:
> $ svnadmin load test <npanday-staged.dump
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2941) import NPanday revisions into
incubator
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated INFRA-2941:
--------------------------------
Attachment: npanday.r1289-1296.dump.bz2
here are the additional revisions up until the latest in Codeplex (which is now frozen). Can we load that into the test-repo? If successful, the final import can go from there.
> import NPanday revisions into incubator
> ---------------------------------------
>
> Key: INFRA-2941
> URL: https://issues.apache.org/jira/browse/INFRA-2941
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Brett Porter
> Assignee: Gavin
> Attachments: base.dump.bz2, npanday.r1289-1296.dump.bz2
>
>
> NPanday is hosted at Codeplex. As the bridge over TFS is not compatible with svnsync, to get a dump we will need to reapply the revisions to a staged repository, then dump that and import it into the test repository.
> The NPanday developers would like to continue the history from the NMaven podling that it forked from. To prepare the staged repository for the above process and keep the history, we'd follow the process below.
> First, create the podling location:
> $ svn mkdir https://svn.apache.org/repos/asf/incubator/npanday
> (take note of the revision, let's call it $REV)
> $ svn cp https://svn.apache.org/repos/asf/incubator/nmaven/branches/NMAVEN_0.14@667430 https://svn.apache.org/repos/asf/incubator/npanday/trunk
> On the ASF repository:
> $ svnadmin dump -r$REV:HEAD asf >npanday.dump
> $ svndumpfilter include incubator/npanday incubator/nmaven <npanday.dump >npanday-filtered.dump
> Then to prepare staging elsewhere:
> $ svnadmin create new-staged-repo
> $ svn mkdir file://$PWD/new-staged-repo/incubator
> $ svnadmin load new-staged-repo <npanday-filtered.dump
> take note of the revision, let's call it $NEWREV
> ... apply codeplex revisions ...
> $ svnadmin dump -r$NEWREV:HEAD new-staged-repo >npanday-staged.dump
> edit dump file to remove first revision content (ie, r$NEWREV)
> Back on the ASF repository:
> $ svnadmin load test <npanday-staged.dump
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2941) import NPanday revisions into
incubator
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated INFRA-2941:
--------------------------------
Attachment: (was: base.dump.bz2)
> import NPanday revisions into incubator
> ---------------------------------------
>
> Key: INFRA-2941
> URL: https://issues.apache.org/jira/browse/INFRA-2941
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Brett Porter
> Assignee: Gavin
> Attachments: base.dump.bz2
>
>
> NPanday is hosted at Codeplex. As the bridge over TFS is not compatible with svnsync, to get a dump we will need to reapply the revisions to a staged repository, then dump that and import it into the test repository.
> The NPanday developers would like to continue the history from the NMaven podling that it forked from. To prepare the staged repository for the above process and keep the history, we'd follow the process below.
> First, create the podling location:
> $ svn mkdir https://svn.apache.org/repos/asf/incubator/npanday
> (take note of the revision, let's call it $REV)
> $ svn cp https://svn.apache.org/repos/asf/incubator/nmaven/branches/NMAVEN_0.14@667430 https://svn.apache.org/repos/asf/incubator/npanday/trunk
> On the ASF repository:
> $ svnadmin dump -r$REV:HEAD asf >npanday.dump
> $ svndumpfilter include incubator/npanday incubator/nmaven <npanday.dump >npanday-filtered.dump
> Then to prepare staging elsewhere:
> $ svnadmin create new-staged-repo
> $ svn mkdir file://$PWD/new-staged-repo/incubator
> $ svnadmin load new-staged-repo <npanday-filtered.dump
> take note of the revision, let's call it $NEWREV
> ... apply codeplex revisions ...
> $ svnadmin dump -r$NEWREV:HEAD new-staged-repo >npanday-staged.dump
> edit dump file to remove first revision content (ie, r$NEWREV)
> Back on the ASF repository:
> $ svnadmin load test <npanday-staged.dump
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2941) import NPanday revisions into
incubator
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906180#action_12906180 ]
Brett Porter commented on INFRA-2941:
-------------------------------------
the test dump is here: http://people.apache.org/~brett/npanday.dump.bz2
it's missing the last 5 or 6 revisions from codeplex added in the last few days. I'll add them after the final release there on Monday, but this should be ok to test with.
> import NPanday revisions into incubator
> ---------------------------------------
>
> Key: INFRA-2941
> URL: https://issues.apache.org/jira/browse/INFRA-2941
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Brett Porter
>
> NPanday is hosted at Codeplex. As the bridge over TFS is not compatible with svnsync, to get a dump we will need to reapply the revisions to a staged repository, then dump that and import it into the test repository.
> The NPanday developers would like to continue the history from the NMaven podling that it forked from. To prepare the staged repository for the above process and keep the history, we'd follow the process below.
> First, create the podling location:
> $ svn mkdir https://svn.apache.org/repos/asf/incubator/npanday
> (take note of the revision, let's call it $REV)
> $ svn cp https://svn.apache.org/repos/asf/incubator/nmaven/branches/NMAVEN_0.14@667430 https://svn.apache.org/repos/asf/incubator/npanday/trunk
> On the ASF repository:
> $ svnadmin dump -r$REV:HEAD asf >npanday.dump
> $ svndumpfilter include incubator/npanday incubator/nmaven <npanday.dump >npanday-filtered.dump
> Then to prepare staging elsewhere:
> $ svnadmin create new-staged-repo
> $ svn mkdir file://$PWD/new-staged-repo/incubator
> $ svnadmin load new-staged-repo <npanday-filtered.dump
> take note of the revision, let's call it $NEWREV
> ... apply codeplex revisions ...
> $ svnadmin dump -r$NEWREV:HEAD new-staged-repo >npanday-staged.dump
> edit dump file to remove first revision content (ie, r$NEWREV)
> Back on the ASF repository:
> $ svnadmin load test <npanday-staged.dump
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2941) import NPanday revisions into
incubator
Posted by "Ulrich Stärk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ulrich Stärk updated INFRA-2941:
--------------------------------
Parent: INFRA-2963
Issue Type: Sub-task (was: Task)
> import NPanday revisions into incubator
> ---------------------------------------
>
> Key: INFRA-2941
> URL: https://issues.apache.org/jira/browse/INFRA-2941
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Brett Porter
>
> NPanday is hosted at Codeplex. As the bridge over TFS is not compatible with svnsync, to get a dump we will need to reapply the revisions to a staged repository, then dump that and import it into the test repository.
> The NPanday developers would like to continue the history from the NMaven podling that it forked from. To prepare the staged repository for the above process and keep the history, we'd follow the process below.
> First, create the podling location:
> $ svn mkdir https://svn.apache.org/repos/asf/incubator/npanday
> (take note of the revision, let's call it $REV)
> $ svn cp https://svn.apache.org/repos/asf/incubator/nmaven/branches/NMAVEN_0.14@667430 https://svn.apache.org/repos/asf/incubator/npanday/trunk
> On the ASF repository:
> $ svnadmin dump -r$REV:HEAD asf >npanday.dump
> $ svndumpfilter include incubator/npanday incubator/nmaven <npanday.dump >npanday-filtered.dump
> Then to prepare staging elsewhere:
> $ svnadmin create new-staged-repo
> $ svn mkdir file://$PWD/new-staged-repo/incubator
> $ svnadmin load new-staged-repo <npanday-filtered.dump
> take note of the revision, let's call it $NEWREV
> ... apply codeplex revisions ...
> $ svnadmin dump -r$NEWREV:HEAD new-staged-repo >npanday-staged.dump
> edit dump file to remove first revision content (ie, r$NEWREV)
> Back on the ASF repository:
> $ svnadmin load test <npanday-staged.dump
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2941) import NPanday revisions into
incubator
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903147#action_12903147 ]
Brett Porter commented on INFRA-2941:
-------------------------------------
our initial attempt on this failed, as I didn't realise that dumping the ASF repo for a single revision would be as large as it was.
I'm currently pursuing another alternative to create an SVN dump from codeplex that I think I'll be able to load in the same way using rsvndump. It looks like taking several days to reconstruct some of the history though, due to a quirk in the way codeplex does it's svn bridge.
However, to test we would need a test repo with at least the content currently in /incubator/npanday (though not necessarily with its history).
> import NPanday revisions into incubator
> ---------------------------------------
>
> Key: INFRA-2941
> URL: https://issues.apache.org/jira/browse/INFRA-2941
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Brett Porter
>
> NPanday is hosted at Codeplex. As the bridge over TFS is not compatible with svnsync, to get a dump we will need to reapply the revisions to a staged repository, then dump that and import it into the test repository.
> The NPanday developers would like to continue the history from the NMaven podling that it forked from. To prepare the staged repository for the above process and keep the history, we'd follow the process below.
> First, create the podling location:
> $ svn mkdir https://svn.apache.org/repos/asf/incubator/npanday
> (take note of the revision, let's call it $REV)
> $ svn cp https://svn.apache.org/repos/asf/incubator/nmaven/branches/NMAVEN_0.14@667430 https://svn.apache.org/repos/asf/incubator/npanday/trunk
> On the ASF repository:
> $ svnadmin dump -r$REV:HEAD asf >npanday.dump
> $ svndumpfilter include incubator/npanday incubator/nmaven <npanday.dump >npanday-filtered.dump
> Then to prepare staging elsewhere:
> $ svnadmin create new-staged-repo
> $ svn mkdir file://$PWD/new-staged-repo/incubator
> $ svnadmin load new-staged-repo <npanday-filtered.dump
> take note of the revision, let's call it $NEWREV
> ... apply codeplex revisions ...
> $ svnadmin dump -r$NEWREV:HEAD new-staged-repo >npanday-staged.dump
> edit dump file to remove first revision content (ie, r$NEWREV)
> Back on the ASF repository:
> $ svnadmin load test <npanday-staged.dump
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-2941) import NPanday revisions into incubator
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin closed INFRA-2941.
------------------------
Assignee: (was: Gavin)
Resolution: Fixed
Done.
Was imported in two steps.
r218 which became r993858 initially failed but succeeded ona 2nd run.
> import NPanday revisions into incubator
> ---------------------------------------
>
> Key: INFRA-2941
> URL: https://issues.apache.org/jira/browse/INFRA-2941
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Brett Porter
> Attachments: base.dump.bz2, npanday.r1289-1296.dump.bz2
>
>
> NPanday is hosted at Codeplex. As the bridge over TFS is not compatible with svnsync, to get a dump we will need to reapply the revisions to a staged repository, then dump that and import it into the test repository.
> The NPanday developers would like to continue the history from the NMaven podling that it forked from. To prepare the staged repository for the above process and keep the history, we'd follow the process below.
> First, create the podling location:
> $ svn mkdir https://svn.apache.org/repos/asf/incubator/npanday
> (take note of the revision, let's call it $REV)
> $ svn cp https://svn.apache.org/repos/asf/incubator/nmaven/branches/NMAVEN_0.14@667430 https://svn.apache.org/repos/asf/incubator/npanday/trunk
> On the ASF repository:
> $ svnadmin dump -r$REV:HEAD asf >npanday.dump
> $ svndumpfilter include incubator/npanday incubator/nmaven <npanday.dump >npanday-filtered.dump
> Then to prepare staging elsewhere:
> $ svnadmin create new-staged-repo
> $ svn mkdir file://$PWD/new-staged-repo/incubator
> $ svnadmin load new-staged-repo <npanday-filtered.dump
> take note of the revision, let's call it $NEWREV
> ... apply codeplex revisions ...
> $ svnadmin dump -r$NEWREV:HEAD new-staged-repo >npanday-staged.dump
> edit dump file to remove first revision content (ie, r$NEWREV)
> Back on the ASF repository:
> $ svnadmin load test <npanday-staged.dump
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (INFRA-2941) import NPanday revisions into
incubator
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin reassigned INFRA-2941:
----------------------------
Assignee: Gavin
> import NPanday revisions into incubator
> ---------------------------------------
>
> Key: INFRA-2941
> URL: https://issues.apache.org/jira/browse/INFRA-2941
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Brett Porter
> Assignee: Gavin
> Attachments: base.dump.bz2
>
>
> NPanday is hosted at Codeplex. As the bridge over TFS is not compatible with svnsync, to get a dump we will need to reapply the revisions to a staged repository, then dump that and import it into the test repository.
> The NPanday developers would like to continue the history from the NMaven podling that it forked from. To prepare the staged repository for the above process and keep the history, we'd follow the process below.
> First, create the podling location:
> $ svn mkdir https://svn.apache.org/repos/asf/incubator/npanday
> (take note of the revision, let's call it $REV)
> $ svn cp https://svn.apache.org/repos/asf/incubator/nmaven/branches/NMAVEN_0.14@667430 https://svn.apache.org/repos/asf/incubator/npanday/trunk
> On the ASF repository:
> $ svnadmin dump -r$REV:HEAD asf >npanday.dump
> $ svndumpfilter include incubator/npanday incubator/nmaven <npanday.dump >npanday-filtered.dump
> Then to prepare staging elsewhere:
> $ svnadmin create new-staged-repo
> $ svn mkdir file://$PWD/new-staged-repo/incubator
> $ svnadmin load new-staged-repo <npanday-filtered.dump
> take note of the revision, let's call it $NEWREV
> ... apply codeplex revisions ...
> $ svnadmin dump -r$NEWREV:HEAD new-staged-repo >npanday-staged.dump
> edit dump file to remove first revision content (ie, r$NEWREV)
> Back on the ASF repository:
> $ svnadmin load test <npanday-staged.dump
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2941) import NPanday revisions into
incubator
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900958#action_12900958 ]
Brett Porter commented on INFRA-2941:
-------------------------------------
rev to dump from is 987684
i.e.
svnadmin dump -r987684:HEAD asf >npanday.dump
(can probably replace HEAD with the upper limit to include the two revisions.)
> import NPanday revisions into incubator
> ---------------------------------------
>
> Key: INFRA-2941
> URL: https://issues.apache.org/jira/browse/INFRA-2941
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Brett Porter
>
> NPanday is hosted at Codeplex. As the bridge over TFS is not compatible with svnsync, to get a dump we will need to reapply the revisions to a staged repository, then dump that and import it into the test repository.
> The NPanday developers would like to continue the history from the NMaven podling that it forked from. To prepare the staged repository for the above process and keep the history, we'd follow the process below.
> First, create the podling location:
> $ svn mkdir https://svn.apache.org/repos/asf/incubator/npanday
> (take note of the revision, let's call it $REV)
> $ svn cp https://svn.apache.org/repos/asf/incubator/nmaven/branches/NMAVEN_0.14@667430 https://svn.apache.org/repos/asf/incubator/npanday/trunk
> On the ASF repository:
> $ svnadmin dump -r$REV:HEAD asf >npanday.dump
> $ svndumpfilter include incubator/npanday incubator/nmaven <npanday.dump >npanday-filtered.dump
> Then to prepare staging elsewhere:
> $ svnadmin create new-staged-repo
> $ svn mkdir file://$PWD/new-staged-repo/incubator
> $ svnadmin load new-staged-repo <npanday-filtered.dump
> take note of the revision, let's call it $NEWREV
> ... apply codeplex revisions ...
> $ svnadmin dump -r$NEWREV:HEAD new-staged-repo >npanday-staged.dump
> edit dump file to remove first revision content (ie, r$NEWREV)
> Back on the ASF repository:
> $ svnadmin load test <npanday-staged.dump
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.