-
Notifications
You must be signed in to change notification settings - Fork 295
Missing git history from coreos-kubernetes/tree/master/multi-node/aws #3
Comments
Hi @kenden I've just finished recovering the history with the procedure you've provided. It does seem to work but a gotcha(at least for me) is that, even though it doesn't relate to the procedure, each directory's history doesn't survive Are you satisfied to the result? Also, regarding the former repo, would you please wait until coreos guys make an announcement? |
Much nicer thanks @mumoshu! |
@kenden I wasn't aware of it but |
@kenden FYI regarding the former repo, coreos/coreos-kubernetes#751 is WIP |
I guess you've probably noticed that the move from the coreos-kubernetes to the kube-aws repo is announced multiple times in github issues. There's also a notice in the very beginning of the README 👍 I'm closing this as the original issues are resolved but feel free to reopen if necessary. |
…RUN-343-userdata-fingerprint to hcom-flavour * commit '0628bedf91b8901b8d220c2e7368b12b84769798': Repair CF rollbacks to work after the S3 userdata improvement Fixes kubernetes-retired#352
Co-authored-by: Kevin Richardson <[email protected]> Co-authored-by: Dominic Gunn <[email protected]>
The first commit message in this repo says:
"Move everything under the multi-node/aws directory from coreos/coreos-kubernetes c25ac21"
But all the commit history from the original location is lost
https://github.com/coreos/coreos-kubernetes/tree/master/multi-node/aws
Could you maybe extract the directory's history?
http://stackoverflow.com/questions/1662753/export-subtree-in-git-with-history
Also, should https://github.com/coreos/coreos-kubernetes/tree/master/multi-node/aws be stopped/blocked if this repo is to become the official location?
The text was updated successfully, but these errors were encountered: