Opened 9 years ago

Closed 9 years ago

#3405 closed defect (fixed)

torperf svn still looks active

Reported by: arma Owned by: karsten
Priority: Low Milestone:
Component: Archived/Torperf Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

https://svn.torproject.org/svn/torperf/trunk/ looks like it's the real torperf repository. It's only if you happen to read the README that you learn otherwise.

I think we should branch it (or tag it -- whichever it is we're supposed to do in svn) as it was before the move to git, and then drop everything from trunk but the README.

Child Tickets

Change History (3)

comment:1 Changed 9 years ago by arma

And if this turns out to be a good idea, we might audit the other tools (like weather) that look like they migrated from svn to git but didn't ever tell the svn users to expect no more changes.

comment:2 in reply to:  description Changed 9 years ago by karsten

Replying to arma:

I think we should branch it (or tag it -- whichever it is we're supposed to do in svn) as it was before the move to git, and then drop everything from trunk but the README.

There are no changes in SVN that are not contained in Git (besides r23159 "torperf moved to git, update the readme accordingly"). I'm not sure what branch or tag you mean here, but I think it's safe to just remove everything from trunk but the README.

Should I do that?

comment:3 Changed 9 years ago by karsten

Resolution: fixed
Status: newclosed

Removed everything except the README file which points to the Git repo. No need to create a tag, I think. The SVN history is also contained in the Git repo. Closing.

Note: See TracTickets for help on using tickets.