<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Fair enough. I updated documentation on <a href="https://github.com/phase4ground/ka9q-sdr" class="">https://github.com/phase4ground/ka9q-sdr</a> to include a reference to your repos, and created an issue (<a href="https://github.com/phase4ground/ka9q-sdr/issues/7" class="">https://github.com/phase4ground/ka9q-sdr/issues/7</a>) to track progress on mirrorring. <div class=""><br class=""></div><div class="">Cheers,</div><div class=""> Jan</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Dec 6, 2018, at 3:53 PM, Phil Karn <<a href="mailto:karn@ka9q.net" class="">karn@ka9q.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 12/6/18 15:37, Jan Schiefer wrote:<br class=""><blockquote type="cite" class="">Do you have a guess how often you will update these? I will set up semi-automatic mirroring of some sort, probably just stick incoming changes onto a branch in phase4ground/ka9q-sdr. Polling the file with a cron job is probably the way to go, unless you can recommend something fancier.<br class=""></blockquote><br class="">As with any project, it'll depend on how active I happen to be. It's so<br class="">easy to update a website tarball (tar, then rsync) that (unlike github)<br class="">keeping my public copy in sync with my actual work is no problem at all.<br class=""><br class="">A mirror would still be appreciated, if only as another offsite backup.<br class="">Can't ever have too many. Thanks.<br class=""><br class="">Phil<br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>