Bonjour,

I think it's not possible to restart the same repos throw the rev 8,000 without 
last dependancys with the previous revisions. 

AS solution I made some think like this for a las demand: you can create a new 
repos and import in the revion n° 8,000 as a new project after wich you add all 
newer revisons. For adding automatically all the newer rev, you can develop a 
script tha extract revision from last repos one by one and add each revion in 
the order on the new repos. In the end you do have 13,000 - 8,000 + 1 revisions 
at all with  perhaps some 2 or 3 auther revisions necessary for creating the 
trunk, branches...




-----Message d'origine-----
De : [email protected] [mailto:[email protected]] De la 
part de MolotovSoup
Envoyé : mercredi 17 août 2011 15:05
À : [email protected]
Objet : [Trac] Subversion Repo Splitting / Trac Survival


Hey guys,

I have an SVN repo that has over 13,000 revisions and I intend to split the
repo at rev 8,000 and archive the previous revisions. The only issue I'm
seeing about this is Trac. I currently have Trac on the entire repository,
but when I split it I'm sure that Trac will break. Is there a way that I can
recover Trac to run on just revision 8,000 and newer?

Thanks!
-- 
View this message in context: 
http://old.nabble.com/Subversion-Repo-Splitting---Trac-Survival-tp32279993p32279993.html
Sent from the Trac Users mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" 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-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" 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-users?hl=en.

Reply via email to