Following xavishayx‘s lead, here’s what I learned today:
When working on a patch to mercurial to show child changeset links in the web interface, make sure you’re testing it on a changeset that actually has child changesets. D’oh!
Following xavishayx‘s lead, here’s what I learned today:
When working on a patch to mercurial to show child changeset links in the web interface, make sure you’re testing it on a changeset that actually has child changesets. D’oh!
RSS feed for comments on this post. TrackBack URI
Good lesson
I believe this falls under the same category as:
make sure you compile the changes to your code before you test them
make sure you copy the bzimage to the kernel you just recompiled before you reboot and don’t see the changes
etc.
Comment by xavishayx — December 31, 2005 @ 7:28 PM |
Re: Good lesson
– make sure you’re running the code you changed
– make sure you changed the correct copy of the code
– make sure the changes you’re testing aren’t bogus because of an earlier change you made
– etc, etc, ad infinitum, ad nauseaum
Experience
n. The wisdom that enables us to recognize as an undesirable old acquaintance the folly that we have already embraced.
Also: http://www.goldshmidt.org/patterns/stupid/index.html. Additions happily accepted!
Comment by mulix — December 31, 2005 @ 9:46 PM |