![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Tracking the original source of an edit
Jul. 13th, 2009 03:00 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
sophieSometimes, it's useful to be able to track how a change made its way into the codebase to start with, for tracking why something is a certain way when it seems totally nonsensical or non-obvious.
Fortunately, it's easy to do so with the versioning systems that Dreamwidth and LiveJournal use, which track every single change made to the source code. (It's quite literally possible to specify any arbitrary date and pull a complete copy of the source code as it was on that date.) In this post, I'm going to use this feature to track down the original source of the FIXME thatfoxfirefey mentioned in her wonderful bug walkthrough, to try to see if it's possible to find out what it's for.
( Walking down Memory Lane... )
Fortunately, it's easy to do so with the versioning systems that Dreamwidth and LiveJournal use, which track every single change made to the source code. (It's quite literally possible to specify any arbitrary date and pull a complete copy of the source code as it was on that date.) In this post, I'm going to use this feature to track down the original source of the FIXME that
foxfirefey mentioned in her wonderful bug walkthrough, to try to see if it's possible to find out what it's for.( Walking down Memory Lane... )
