[ctdonath]

"When" too. Nice to know whether the weirdness was added last week or last decade. I've left old obtuse comments in place just as proof that the function, as written, was there for the last 14 years (which sometimes explained a lot).

[Ensorceled]

I don't find when useful, except in post mortem situations. The code is the code. Trying to capture history leads to things like old code being commented out to preserve the context. Use a good code repository instead.

[mercurial]

git annotate?

[ctdonath]

I'm talking code that has out-lived several "yeah we'll use this forever" version control systems. If the comment isn't in the code it will get lost.

[ZoFreX]

FWIW you can actually migrate between most major VCS systems without losing your history.

[Someone]

Yes, but it is neigh impossible to migrate from say Python to C, a copy-paste into an entirely different project, and from there via Java to C# and keep history. That may be a stretch, but even one such step will almost certainly lose history.

[mercurial]

It also depends on what kind of stuff you've done with your VCS. "Creative" SVN layouts may be difficult to merge.

[ctdonath]

That's assuming somebody remembers where it was.