Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find outdated fixed CodingTracker sequences #342

Open
reprogrammer opened this issue Feb 4, 2012 · 1 comment
Open

Find outdated fixed CodingTracker sequences #342

reprogrammer opened this issue Feb 4, 2012 · 1 comment
Assignees

Comments

@reprogrammer
Copy link
Collaborator

Some CodingTracker sequences need to get post-processed to be parsed and replayed correctly. We store the fixed CodingTracker sequences in a Subversion repository different from our main data repository. If a user updates his or her original CodingTracker sequence, the fixed CodingTracker sequence becomes outdated, because it no longer contains the new changes. I suggest that we write a script to detect the fixed CodingTracker sequences that have become outdated.

@ghost ghost assigned reprogrammer Feb 4, 2012
reprogrammer added a commit that referenced this issue Feb 4, 2012
@reprogrammer
Copy link
Collaborator Author

@Wanderer777 The script find-outdated-fixed-change-sequences.rb found only the following outdated fixed CodingTracker sequence:

"relative path of fixed CodingTracker sequence","fixed revision","last changed revision"
"cs-512/7e76e17c-a09e-4adf-8035-6841cad0d0e0/1.0.0.201107172332/codingtracker/codechanges.txt",2274,2335

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant