theupdateframework
Preserve history?
It's not a big deal, but it's too bad we lost a lot of git history in moving the specification to a new repository.
No need for despair. The original specification and its full git history was preserved.
The text of the original file was edited to note the specification's new home (this repository).
Cheers!
Should we provide a link to the original file? I wonder if others are also interested in the specification's git history.
Hey @vladimir-v-diaz, long time!
I understand the history is there in the old repository, but it would have been nice to preserve it in the new one.
Oh, well, maybe next time :)
👍 I agree w/ Trishank: almost always worth transferring history. It takes a little bit of tinkering, but it's not too bad.
At this point, it could still be worth doing it (rebuilding the master branch locally in a new splitting of the old repo, cherry-picking the 23 commits that are currently in this repo, and then force pushing the new branch to recover the full history), but perhaps not. There seem to be enough people following the new one already that it might be disruptive. I'm not sure.
Edit: Didn't realize this was as old as it was. Sorry for the resurrection. (:
yeah, it's a little sad that the complete history of the specification has not been preserved, because lots of people worked on it. oh, well.