4 ms·
99.9% of people will only care about the current version. So don't worry too much about history, people mostly just want stuff that is accessible and works. Ed
by Raed667 5y ago
99.9% of people will only care about the current version. So don't worry too much about history, people mostly just want stuff that is accessible and works.
Edit for clarification: You can delete the history for the open-source version and publish it with a fresh history. And keep the original history internally in case it is ever needed.
- dschuessler 5y agoThis is breathtakingly bad advice from a security perspective. If secrets might sit around in a repository you don't just publish it and bet on people not looking for them, at least not if data security is of any worth to you.
- Raed667 5y agoThat is not what i said. I said he should delete history and publish a new version with a new commit "v1"
- dschuessler 5y agoYou literally edited that in after my answer.
- winter_squirrel 5y agoHe added clarification, but his original comment still implied the same thing
- madeofpalk 5y agoGosh I wish there was a history available so I could understand all this context!
- OJFord 5y agoRead it in the context of OP's question - GP is suggesting squashing all history and not worrying about it, as OP alluded to.
- dschuessler 5y agoYes, I see how it can be understood that way. GP has edited it anyways to clarify this point.
- kissgyorgy 5y agoHistory is way more important than the current version of the code.
- thrower123 5y agoI've had managers tell me this when we've had to cut over from SVN to git. Maybe it's true for them... For me out on the pointy end of the spear, it's not hard to bring that history across, you just have to know how to do it, and it's invaluable when you're trying to figure out bugs.
- blagie 5y agoIt's not a numbers game. The remaining 0.1% can be very important too. There are times to kill history, and there are times to bring it along. History does a lot of things. - Giving people credit. - If, in 20 years, you want to pull up an old (no-longer-compatible) document - Public patent prior art - ... and a swarm of others "Internally" is likely to no longer exist a decade down the line. Whenever I've open sourced, I've brought along history. In one case, we did need to rewrite history to remove a few sensitive files, but git makes that easy enough. If keeping history is a heroic effort, by all means kill it. However, that's not a good generic best pracitce.