Re: RCS, again: another removed functionality: undo last-checkin

[Stefan Monnier]

[ Sending in private, it's only for information.  ]

> LilyPond works with a "staging" branch and a "master" branch.  "master"
> only moves forward: once a commit is in there, it stays.  If its effects
> are to be annulled, it is reverted.  Nobody pushes to master though.
> Any changes are instead pushed to staging.  An automated task picks up

Sounds like an attractive organization.

One question, tho: how do you deal with (aka "synchronize") concurrent
"push" to the staging branch, if you allow the staging branch to be
"forced" (either via non-FF, or via remove+push)?


        Stefan