On Tue, May 12, 2009 at 03:25:53PM +0200, Jan Pazdziora wrote: > > > > Jan, is there something I can do to edit that message and get this push > > to work? > > The one of d1c65b572d1b9e1ccd863cce3104a853acc9ad9f? Nope. The best > bet will probably be to ask the infrastructure guys to disable the > hook, do the push, and enable it again. Upon subsequent pushes, the > commit will already not be considered by the hook.
I was thinking about this more. Can't you merge the commit just before the merge commit which causes a trouble, then cherry pick that commit's change with normal commit, and then merge the HEAD? That way, the git rev-list could be reporting the new non-merge commit, not the merge one. Could you give it a try? -- Jan Pazdziora Senior Software Engineer, Satellite Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
