Hello, Igor Plyatov wrote: > Hello! > > Due to bug-hunting on NMEA reference clock driver, I have conversation at > NTP Bug Tracker - https://bugs.ntp.org/show_bug.cgi?id=3611. > > Where the Juergen Perliner wrote >> The repo is in >> psp.ntp.org:~perlinger/ntp-stable-3611 > > Please somebody explain how exactly can I clone that repo to see a bug-fix > (source code changes) for issue #3611?
The repo is a private cloned repo of Juergen Perlinger, located in his home directory on one of the computers of the NTP project. Changes only become visible to the public after they have been merged into the public repo. But of course, if Juergen agrees, he can send you a copy of the code, or a patch with the changes he made. > I ask, because for me, as for typical GIT user, such URI to repo is not > clear at > all. And no information about psp.ntp.org host. Hm, if you have a private branch of a git repo then no one else can see this, either. > I have read about repo cloning at > http://support.ntp.org/bin/view/Main/SoftwareDevelopment. This is if you want to clone the repo with the changes that are already public. > I've cloned https://github.com/ntp-project/ntp, bk://bk.ntp.org/ntp-dev, > bk://bk.ntp.org/ntp-stable and all of them outdated. Latest commit in > them is > from 2016 year, irrespective to repo transport - is it a GIT or BitKeeper. That was an attempt to move the BK repo including its history to github. Unfortunately this was not completed due to missing maintainers. Martin _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
