So I'm trying to pretty up some commit id's with a simple mining script. (Yea, I know, but I figure 5K sha tests isn't that bad).
Here's my initial branch keybounceMBP:paperclips michael$ git branch -lv FrankV3 1f47df5 initial * Interface 1f47df5 initial master 1f47df5 initial Here's that commit keybounceMBP:paperclips michael$ git cat-file commit 1f47 tree b6c509f8022343bb7d87aad6281fc5da90b2c446 author keybounce <[email protected]> 1508798663 -0700 committer keybounce <[email protected]> 1508798663 -0700 initial Here's the mined sequential number keybounceMBP:paperclips michael$ git cat-file commit 001f20ce5db86b1d13eb7cc27c7dd4c9d8a32218 tree b6c509f8022343bb7d87aad6281fc5da90b2c446 author keybounce <[email protected]> 1508798663 -0700 committer keybounce <[email protected]> 1508798663 -0700 initial [6413] So this should replace the old reference safely, right? keybounceMBP:paperclips michael$ git update-ref ref/heads/master 001f20ce5db86b1d13eb7cc27c7dd4c9d8a32218 keybounceMBP:paperclips michael$ git branch -lv FrankV3 1f47df5 initial * Interface 1f47df5 initial master 1f47df5 initial keybounceMBP:paperclips michael$ Part of me thinks that I could just go into the refs directory and alter the files directly. But then I notice that those shas are seen elsewhere, at least in the reflog, and possibly (probably?) elsewhere. So I don't even know how to safely update a reference, and the tool doesn't seem to work for me. Help? --- Entertaining minecraft videos http://YouTube.com/keybounce -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
