-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation unclear on whether chg-multi is deprecated #159
Comments
That wiki page is for the As the NOTE says:
The chg-multi changer is still supported. |
Oh, that makes sense. Perhaps someone with edit access to the wiki could make it clear that the wiki page is only about the old |
I suspect that page could just be deleted! I don't have permission, though. It's really more like 12 years -- I was the one to build the "changer API 2.0" and I haven't worked on this for 10 years.. |
That zmanda-wiki is outdated and neglected like the community edition of amanda. I also don't have access anymore, for years. @chassell pls reopen and fix that wiki or let's for example transfer the content into a wiki here on github, where people could contribute. |
@stefangweichinger we just turned the wiki OFF because we found tons of spam being uploaded apparently to help serve text output of some type if you craft the URL just right. slimey. When it is up... I probably will not maintain it but we should get you back into it. Afraid to say I'm not sure when they'll have it up! Darnit. |
@chassell thanks for the status. That wiki-content needs an overhaul as well, sure. Totally understandable that you won't be able to maintain code and docs all on your own, right. I wonder if we could get the community to contribute as well. |
The wiki page for chg-multi has a big red banner saying
chg-multi
is deprecated. However, the documentation for the diskflat device, which was added very recently, also claims thatchg-multi
is the only way to use diskflat. This is confusing. Ischg-multi
deprecated? If not, why does the documentation say it is? If so, why was a new feature added in 3.4.4 that requires its use?The text was updated successfully, but these errors were encountered: