<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Aug 20, 2016 at 11:44 PM, Ian Wadham <span dir="ltr"><<a href="mailto:iandw.au@gmail.com" target="_blank">iandw.au@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Fork the repo??</blockquote></div><br>github expects you to do this, yes. I don't actually recommend it because keeping up to date with the original repo's a PITA (and *not* automated in any way. <a href="https://help.github.com/articles/syncing-a-fork/">https://help.github.com/articles/syncing-a-fork/</a> is annoyingly manual). You lose the ability to maintain your clone with github's web interface, but that's not much of a loss really. (Or you can do their thing in reverse: clone the repo, add github as an additional upstream, create a new empty repo (not a fork) via their web interface, push to github periodically as a backup.)<br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>