tag:blogger.com,1999:blog-3803541356848955053.post7151686160035312203..comments2016-09-28T23:43:19.979-07:00Comments on YJL: Please don’t fork or clone if …Yu-Jie Linhttps://plus.google.com/115422682039760465813[email protected]Blogger4125tag:blogger.com,1999:blog-3803541356848955053.post-14370085411543295882013-04-01T18:42:15.975-07:002013-04-01T18:42:15.975-07:00Kids on facebook have 131232132 friends, [...]
Ah...Kids on facebook have 131232132 friends, [...] <br />Aha! Now everything is so clear to me. Those darn kids! ;)<br /><br />And I totally forgot they have to continuously sync repo in order to have "save copies." So, my point is stronger now. All they do is keeping useless trash.<br /><br />Sincerely yours,<br />Yu-Jie Linlivibetterhttp://yjl.im/[email protected]tag:blogger.com,1999:blog-3803541356848955053.post-53616045249560258352013-04-01T16:47:59.464-07:002013-04-01T16:47:59.464-07:00Basically hoarding clones is done "because it...Basically hoarding clones is done "because its cool". Kids on facebook have 131232132 friends, kids on Github/GCode have 21321321 forks. I've once heard philosophy behind is to keep safe copies of software just in case author decides to remove his repo, but then reason would advise you to sync it regularly, and thats something hoarders dont do.rafalp[email protected]tag:blogger.com,1999:blog-3803541356848955053.post-15131915741241548902013-01-31T03:03:33.291-08:002013-01-31T03:03:33.291-08:00[...] when software is done.
done meaning the sof...[...] when software is done.<br /><br /><i>done</i> meaning the software stops being updated or actively developed?<br /><br />I still don't get it. When a software is good, so you clone the repo to your <i>local storage</i> and you have full history of the repo on you disk, assume it's GIt/Hg/etc. It's not going to break as long as the working copy is the one without bugs. Why is there a reason for cloning under your account, then clone it local?<br /><br /><br /><br />If a repo is good, then it's most likely to last forever, the owner knows it, because he or she is good at coding and knows the importance. Even the owner decides to axe their own original repo, since it's good, there must be tons of <b>real</b> cloned/forked repos. It's going to last for eons and eons, really has no to clone if you don't plan to contribute or just to commit some of your modifications.<br /><br /><br />If you clone for "keep my personal setup," then you are not the kind of user I described in my post. The user I mentioned has <i>never committed anything</i> to their publicly cloned/forked repo under their account, not even a config file. I think you misread my post, see the screenshot, only one out of 18 cloned repo has ever been committed with new commit. The rest 17 are just clones with any modifications, don't you think that's a waste of storage?<br /><br /><br /><br />Anyway, still thanks to speak up, even I don't think you are one of those users.livibetterhttp://yjl.im/[email protected]tag:blogger.com,1999:blog-3803541356848955053.post-18091310804408331802013-01-31T02:40:29.446-08:002013-01-31T02:40:29.446-08:00I've some of those repositories and I do it be...I've some of those repositories and I do it because I believe than there is a time when software is done. Whenever I feel it, I clone it and keep it that way for the eternity, I think there are more important things to do that keeping an eye on software which pretty much does want I want, it's also useful to keep my personal setup running without worrying it may break in the future for some random update, specially when dealing with addons.<br /><br />Great blog! =)chilicuil[email protected]