Given the egregious nature of the log message; I stripped the tip from the
gate and had David push a new changeset with corrected comments. I'm
pretty sure that no one pulled the original changeset, but if you do, the
simplest way to get rid of it is
hg --config extensions.mq= strip 9c9194aad2d782cfbb209bb5a3bb9f8ab0c72cdf
If you don't, you should be notified on pull that a new head is being
created, and you should be notified on push that you're about to create a
new head, and the operation will abort.
Although I *can* do this, I really don't want to get in the habit of doing
it. So please, make sure your comments match your changeset. It helps a
lot if the webrev you send out for review includes the comments, rather
than running webrev over the workspace without a changeset (which is when
you see the "NO COMMENT" comments). David might have seen this sooner if
he didn't have to hand-job his webrevs because webrev produces relatively
useless output for the kind of changes he's making. Something I want to
fix, in my spare time.
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
