Remove PentaDb, PentaBackend, CachingBackend, FDMCommand #237
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(We also didn't use it for the past 2 years)
reivilibre
force-pushed
the
rei/fd25_nopentabackend
branch
from
f625e8f to
f0e60bb
Compare
Half-Shot
approved these changes
Dec 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PentaDband didn't use one last year. Therefore remove this legacy code.PentaBackend— nowadays we use Pretalx (optionally with FOSDEM-specific Pentabarf-style XML)CachingBackendwas specific to thePentaBackendas the other backends had built-in caching, so let's remove that.FDMCommandis totally inoperable without aPentaDband we did not use it for the past 2+ years (I don't know what it does and have never used it, so it's not been used when I've been involved), so let's remove it