Yo Hal!
On Wed, 01 Feb 2017 04:18:24 -0800
Hal Murray wrote:
> It's reasonably easy to setup a cron job to make a copy of the data
> in git. How many of us should do it?
We already use github as a slave to gitlab, so I think out git is covered.
> What do we have in the way of backup for our ot
Hal Murray :
> It's reasonably easy to setup a cron job to make a copy of the data in git.
> How many of us should do it?
Git data and metadata are not the problem. Every pull of any of our
reopositories replicates its entire state. What we risk losing is
tracker data, and possibly the hooks
It's reasonably easy to setup a cron job to make a copy of the data in git.
How many of us should do it?
Is there any way to grab a copy of the issues data?
What do we have in the way of backup for our other stuff? How much is there
that's not on gitlab?
---
A while ago, I signed up fo
* waf needs some tlc
#212 ยท opened a month ago by Hal Murray
updated 3 weeks ago
waf check generates:
```
magic.pyc
control.pyc
version.pyc
magic.pyo
control.pyo
version.pyo
```
waf build should have done all of that. ctx.add_group() is called after the
ctx() calls to build c
Gitlab has had an outage. They are working to recover, but it seems
their backups were hosed and then someone made a finger error. It is
possible that our issues and merge requests have been lost.
Account of the incident here:
https://docs.google.com/document/d/1GCK53YDcBWQveod9kfzW-VCxIABGiryG7
