RFC: Possibility to re-edit last commit message

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jari Aalto wrote:
> This is the problem. I would just need a new message right after the
> old one; with version N+1, if that's the feasible solution. No actual
> file commits whatsoever even if they had changed.

When you talk about version N+1, it's hard to know what you're talking
about.

I think you mean a direct descendant of N.  But my initial impression
was that you thought revision-ids were somehow sequential, because
revision-ids are the only unambiguous way of identifying versions.

> Not removing, keeping it there, but stacked -- where the last one would
> only be visible. But if I understood correct there would have been
> problems.

I'm not sure what "stacked" means, but if "hidden" is an adequate
synonym, it's not entirely impossible.

The problems I see with this are:
- - Do we want to hide this from the user?  Does this open up a security
hole?
- - How pervasive would the changes need to be?  If we're going to hide
revisions, we don't want the revno to increment for hidden revisions, I
expect.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFvpWX0F+nu1YWqI0RAmavAJ4yZ7OTWyELf3UKSMP4S5HACHY10QCfXaBT
mo5icJUWrPoHIwNVTt56MKg=
=8GzX
-----END PGP SIGNATURE-----