"Robert Anderson" <rwa000@xxxxxxxxx> writes: > There are good reasons for desiring a workflow that does not routinely > change history as part of the usual workflow. Maybe there are clones > of your repo. Maybe as part of your workflow discipline you do not > want HEAD states that cannot be pushed to public, because you don't > want to manually keep track of when it is ok and when it is not ok to > push HEAD to public, since git cannot tell you this. Surely you can arrange that. You keep track of what you pushed out, and you refrain from rebasing beyond that point. And fast-forward check in the push to the public will notice if you break that "workflow discipline" by accident. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
