"m...@apollinemike.com" <m...@apollinemike.com> writes: > Sorry for the oversight. Wouldn't it just be easier to commit a new > commit with the change in version number?
Sure, that's certainly possible. However, one of the points of the staging branch is that mistakes need not get into master. To make an example for how to do corrections like that, I looked at your change in order to find something to complain about. And the version string was the easiest target... dev/staging is a moving target. It should be kept in a state where fast-forwarding master to it is possible (because that's really what Patchy can do with good conscience after testing). But from one moment to the next, it might stop being a proper descendant of a previous value of dev/staging, and contributors must be prepared to deal with that: rebasing their own work on top of an old dev/staging on the rewritten version of dev/staging. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
