3 ms·
I only have a working knowledge of git but wouldn't that be equivalent to re-writing the whole history of the repo? Rebasing would give all of the commits a new
by VBprogrammer 7y ago
I only have a working knowledge of git but wouldn't that be equivalent to re-writing the whole history of the repo? Rebasing would give all of the commits a new commit ID and would cause conflicts everywhere.
Unless of course you just meant as an interesting way of being able to see the full history rather than suggesting the project adopt it.
- simcop2387 7y agoGit has the ability to use grafts for this scenario. https://stackoverflow.com/questions/1220557/how-do-i-prepend-history-to-a-git-repository https://stackoverflow.com/questions/1220557/how-do-i-prepend...
- no_identd 7y agoAnd if that's not enough, Eric S. Raymond has written a bunch of absurdly powerful tools for scenarios like this one: http://www.catb.org/esr/reposurgeon/ http://www.catb.org/esr/reposurgeon/ https://gitlab.com/esr/git-debubble https://gitlab.com/esr/git-debubble https://gitlab.com/esr/git-weave https://gitlab.com/esr/git-weave Some background information provided by ESR, in addition to what you can find on the homepage: https://groups.google.com/forum/m/#!topic/golang-nuts/WstriKt2jTA https://groups.google.com/forum/m/#!topic/golang-nuts/WstriK... https://news.ycombinator.com/item?id=22304131 https://news.ycombinator.com/item?id=22304131