Wrong BugID (whoops!)

mark.reinhold at oracle.com mark.reinhold at oracle.com
Tue Jul 9 13:56:38 PDT 2013

2013/7/9 5:50 -0700, dmitry.samersoff at oracle.com:
> 1.
> For cases like this I would like to have a file counting problematic
> changesets e.g. ProblemChangesetList.txt, otherwise it's hard to
> restore the history after couple of years.

I don't understand.  The whole point of removing problematic changesets
is so that they're never part of the long-term history.  Why do you need
a list of them?

In any case, if you do need a list then the hashes of all blacklisted
changesets in OpenJDK repositories are in jcheck.py itself.  (There's
a separate server-side list for Oracle-internal repositories.)

> 2.
> Starting from Mercurial 2.2
> hg has --amend command that allows to perform limited but safe editing
> of the history. Never tried it so not sure it helps in this case.

It doesn't help in this case.  That option only works in a local
repository, on changesets that haven't yet been pushed anywhere else.

- Mark

More information about the hotspot-dev mailing list