#32025: Stop using corpsvn and disable it as a service
---------------------------------------------+----------------------------
Reporter: arma | Owner: tor-gitadm
Type: project | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Service - git | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: #17202 | Points:
Reviewer: | Sponsor:
---------------------------------------------+----------------------------
Comment (by arma):
Replying to [comment:3 arma]:
> (1) Freeze corpsvn (i.e. make it read-only), and make a full checkout of
it somewhere
Oh, and here is what might be a critically useful further observation: I
believe we don't need any svn history or previous versions of things. That
is, I think that the only things we want to rescue, and then triage, are
the current versions of the files in the repo.
So we could do an svn checkout somewhere internally, keep those files
there, and then once we have Sue putting her new files somewhere smarter,
we could shut down the svn service and keep the svn checkout around for
when we do step (3), plus be able to access it in a pinch if Sue somehow
loses her own svn checkout.
(We might want to keep the actual svn database around for a while too,
since e.g. I bet doing an svn checkout on Windows makes the line endings
correct for Windows, and other subtle things that won't be immediately
obvious to us at first.)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32025#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
