![](/static/253f0d9b/assets/icons/icon-96x96.png)
11·
9 months agoI’d save as HTML and then run something to convert it to markdown or some other type of plain text.
Why do you want to delete a post history?
I’d save as HTML and then run something to convert it to markdown or some other type of plain text.
Why do you want to delete a post history?
Stuff can disappear or stop being free at any time for no reason, with no notice.
Have you weeded out or linked any duplicate files first? Might save you some room.
Have you weeded out or linked any duplicate files first? Might save you some room.
First, have a look at these pages for some ideas:
https://github.com/driusan/PoormanIssueTracker
A simple format for using the file system as an issue tracker
https://github.com/driusan/bug
Distributed bug tracking with the filesystem and hg or git, written in Go
https://www.joelonsoftware.com/2000/11/08/painless-bug-tracking/
Nice article by Joel Spolsky about setting up a small bug DB; might also be suitable for use with a spreadsheet
Have you ever used Midnight Commander or a filesystem browser? If you’re comfortable finding your way around a directory tree, here’s a quick and dirty example with your tickets under a folder called “issues”:
You don’t need a bunch of separate files; I like directories in case there are screenshots, email messages, etc. Something like this would also work using (say) dokuwiki.