I'd rather not diverge from homu/homu too much; this PR will make every uplift need merge conflict fixing.

(Also, I'd rather not switch to servo/homu unless we really need to)

(Also, I'd rather not switch to servo/homu unless we really need to)

Homu seems to break every day. How confident are you that your SQLite changes today fixes that?

(Also, I'd rather not switch to servo/homu unless we really need to)

Also, why?

Homu seems to break every day.

AFAICT that was one bit of brokenness introduced due to homu being restarted at the wrong time, which sort of stayed around mucking up the internals and making it keep two pending PRs at all times.

How does switching to servo/homu fix it, even if it was a code issue?

I don't mind switching to get upstream patches faster, I'd rather avoid diverging though.

Also, why?

Just extra work to keep it up to date. I don't like forking unless there's a need; code formatting isn't a need 😄

How does switching to servo/homu fix it, even if it was a code issue?

I was planning to maintain this repository. I wanted to start by incorporating a sane linter.

So, a month later. Have any thoughts about this now?

Update master to homu master first, but sure, merge this!

From what I can tell, servo/homu is up-to-date with barosl/homu, if that's what you're asking

Also, should we get homu set up here in servo/homu? 😛

r+