3 ms·
An easy solution is to split it off to an "Unused" pseudoproject in the source control system. This avoids archeology on historical versions.
by cema 17y ago
An 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. :-)