Comment 0 for bug 73752
Revision history for this message
| Nicholas Allen (nick-allen) wrote Smart server should have ability to prevent commits that change revision history order | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
When multiple developers share the same branch and push to it, it is possible that the revision history order changes. So revision 10 represents a change by one developer at one point in time but after a few merge and push operations by the various developers at a later time revision 10 is no longer the same change by the same developer. This may be undesired for a shared branch and is not possible to prevent on the dumb file server protocols. The only option available to ensure this is to setup PQM and have it as the only one that pushes into the shared branch.
If all developers use checkouts or bound branches the revision history will not change but if some developers don't do this then this will not be the case.
It would be nice if the smart server could optionally enforce the rule that the revision history cannot change (only be appended to). If a user tried to push their changes and the existing revision history would change order then the smart server would report an error to the user explaining that they should use a checkout or bound branch for pushing changes to the shared branch.
I guess this could be implemented by some generic commit hook abilities in the server...