23 Jan
2019
23 Jan
'19
5:17 p.m.
When you fork the nice thing is that you can then "git pull upstream"
and changes will automatically merge down unless there is a conflict.
Graham
On 1/23/19 11:17 AM, op25(a)zellners.com wrote:
Quoting iain macdonnell - N6ML <ar(a)dseven.org>rg>:
If you still have your local clone from before,
and haven't made any
(conflicting) changes, you can just 'cd' there and do 'git pull', then
'./install.sh'.
Otherwise you could make a completely new clone, but if you added any
config files inside the old one, you'd have to copy them over to the
new one.
I no changes, but yeah, I figured the configs would need to be backed
up, as well as the log(s)... I keep the logs for analysis purposes... :)
We'll see if I get this far today in the lab.
Future , I will probably have to fork, and then figure out how to
merge down changes to my fork as I need to make some changes in
places, add some things in a couple areas for my specific needs, which
appear to be already rejected upstream.
git and compiling not my thing... I just updated my python stuff, and
restart. :) No compilers needed. :) ;)
Thanks.