Hacker News Reader

It's true that it will be accessible from the repository, but a few years from deletion, people will forget it is there.

I think that they should've put this right there in the comment, really.

View on HN

If the comment says where to find it in the repository, when you change repositories you have to remember to change the comment. If enough time has passed since you changed repositories, that becomes a problem.

Emacs is an old codebase. It predates modern repositories, or close to it, and it certainly predates the repository it currently uses.

You don't need to update the comment. You just need to make sure that when you change repositories you preserve the mapping of old commit IDs to new commit IDs. git-svn does this by including the SVN revision in the git commit message.

Ahh, but does git-svn-cvs-rcs do this? It's worth remembering that there were still 15 years to go from when this code was commented out to when SVN was invented.

And for that matter, does burguggle-git-svn keep SVN revisions traceable? Or are we assuming git is the pinnacle of software revision control and emacs would never ever change again.

Reply on news.ycombinator.com