4 ms·
Yes, version control does keep it around for you, but often it is not the easiest thing to associate some piece of code with a repo version. I am not advocatin
by fogus 17y ago
Yes, version control does keep it around for you, but often it is not the easiest thing to associate some piece of code with a repo version. I am not advocating keeping chunks of commented-out code around; just saying that I have yet to find an optimal solution to the other side of the problem either.
- cema 17y agoAn easy solution is to split it off to an "Unused" pseudoproject in the source control system. This avoids archeology on historical versions.
- joeyo 17y ago> This avoids archeology on historical versions. It's not really your main point, but the idea of revision control archeology is a really a great analogy.
- holygoat 17y agoI favor a 'scratch' or 'junk' dir in each project. Source that I know I don't need now, but want to keep around. grepping for terms will often find a chunk of code I wrote that nearly solves a new problem. Version control is not so easy to search, particularly if you're looking for a utility that you think is live in the project.
- cema 17y agoYes, grepping a folder is easy. Of course, you can always update it from the source control database. :-)