This looks like an "oops". We shouldn't be force-pushing anything to our maintenance/development branches. We don't want to lose any history, and we don't want to break forks (unless there's a very good reason, discussed on the list first).
It's probably okay to do this on a feature branch, while it's in progress, but not once it's been merged/pushed to a maintenance branch or master. If anybody has the specific extra commits that were previously pushed, then overwritten, please restore them by merging them back in to the 1.6 branch. If you need help, please ask. Thanks. -- Christopher L Tubbs II http://gravatar.com/ctubbsii ---------- Forwarded message ---------- From: <[email protected]> Date: Sun, Jul 26, 2015 at 12:29 AM Subject: Git Push Summary To: [email protected] Repository: accumulo Updated Branches: refs/heads/1.6 b83f88caf -> 967100dda (forced update)
