Guenter wrote: > still on 2.5, and all I could find with goggle is: > git rebase --interactive $parent_of_flawed_commit > is this correct? how to use it?
It looks like it would be correct, but again since you already pushed the bad commit everyone who is pulling from git.stuge.se would have to delete their pulled trees and clone again, and I'm not sure fixing this is worth the effort? There was another config oops for the very first commit that was pushed to git.stuge.se, but we didn't bother fixing that and I don't think this is all that bad either, now that your config is ok. Or? > do I now need to lookup the last commit id > (another pain this 50 hex char thing!) The 40 hex char thing is a hash of the repository contents (files and log) at the time of the commit. Including Author: and Date: headers. All of git will accept shortened commit ids, you only need to type the first few characters that uniquely identify the commit id in the repository. > before my own commit or what? Right. For the commit 8dabb1c5eb2b988612ee12e032ca262c4aed2a2a you could show the parent commit using: git log 8dab^1 -1 (There's also e.g. --pretty=oneline to make scripting easier) ^1 means "go back 1 step" and -1 means "show log for 1 commit" //Peter _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
