Old RethinkDB issues

[CodeX604]

Hi All,

Looks like all the old RethinkDB issues were lost in a merge with RebirthDB.

Is that correct?

Thanks

[ChrisTalman]

The old repository still exists, just under the name rethink-legacy: https://github.com/rethinkdb/rethinkdb-legacy.

An unfortunate side effect of this is that a lot of links and Google search results currently end up in a 404, until you append -legacy to the repository name in the link.

[atris]

We will be redoing the move and old RethinkDB repo will become RethinkDB again. Should happen this weekend

…

On Tue, 2 Oct 2018 at 12:06 AM, Chris Talman ***@***.***> wrote: The old repository still exists, just under the name rethink-legacy: https://github.com/rethinkdb/rethinkdb-legacy. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <rethinkdb/rethinkdb#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABpO42ovpj8R2QGXXA09H-K5OotsABg9ks5ugmCwgaJpZM4XChsE> .

[ChrisTalman]

Nice!

[anatol]

@atris any update? Arch Linux devs started filing tickets because of it. https://bugs.archlinux.org/task/60743

[thelinuxlich]

Unless someone steps in and merge the diff between this repo and rethinkdb-legacy, so we can rename the rethinkdb-legacy repo to rethinkdb again, nothing changes.