Jason,
the return code is 1, this seems to be established (but surprising) git
behaviour, even though it goes against common unix conventions:
http://www.gelato.unsw.edu.au/archives/git/0701/36674.html
If I comment out the sys.exit(1) line 180 in your patch-script, the test
runs through with the expected result:
[steinbrt.tcbpc142 amber]$ ./check_patches.py -b bugfix.8 -a
I will now try applying this patch.
You did not tell me what commit to apply the patch on. I'm guessing
you want the second-newest commit: 3236d34e2daa196766a9cedaf19269f7095b32c9
I could not do a git-status. Not enough resources?
Creating a new branch [am12-test-patch-apply] to test the patch
Created branch [am12-test-patch-apply] -- checking it out and applying the
patch
Patch applied cleanly.
Resetting the branch to the original state.
I am (forcibly) going back to amber12-with-patches now
Deleted branch am12-test-patch-apply (was 3236d34).
The patch appeared to apply cleanly. Please check that the
description printed by patch_amber.py is OK to you. You can
use the -p/--preview flag for this to see how it will appear
So the patch-file seems good, only the checking of error codes from git
status should be changed...
Thomas
Dr. Thomas Steinbrecher
formerly at the
BioMaps Institute
Rutgers University
610 Taylor Rd.
Piscataway, NJ 08854
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Wed Jul 25 2012 - 10:00:04 PDT
