Re: [AMBER-Developers] URGENT: weird commit to master branch at

From: Jason Swails <>
Date: Fri, 20 Apr 2012 17:01:03 -0400

 Some tips derived from experience:

On Fri, Apr 20, 2012 at 12:38 PM, Scott Le Grand <>wrote:

> So the correct answer here was git push origin <commit_id>:spfp-dev?

These sorts of issues only pop up if you reverse history in your local
branch -- if you do this, and your local branch diverges from your remote
branch, git will not let you push to that remote branch peacefully. My
advice here -- never reverse time. If you need to reverse a commit, create
a reverse-patch using git-diff and commit that as a new commit rather than
rewriting history. I would rewrite history only if you are 100% sure that
your changes are not published *anywhere* except your local repository.

I have a git page on my Wiki (linked to in the Coding section of the Amber
Wiki now), that hopefully has most of the information people would need.
For specifically reversing commits, here's my advice: (expanded recently to be more

Noted for the future if so and I sincerely apologize for the breakage...

Like Dave said, it was an easy fix. Furthermore, because git is
distributed, it doesn't matter of the gitosis repo blows up -- there are
dozens of full copies of the repo out there which can easily be used to
rebuild gitosis (still preserving the whole history).

All the best,

Jason M. Swails
Quantum Theory Project,
University of Florida
Ph.D. Candidate
AMBER-Developers mailing list
Received on Fri Apr 20 2012 - 14:30:03 PDT
Custom Search