some might regard it as a predatory publisher
à la con
some might regard it as a predatory publisher
thanks for the reply, but i think i got that. from the linked article:
For example, if you changed repo/packages/foo/CHANGELOG.json, when git was getting ready to do the push, it was generating a diff against repo/packages/bar/CHANGELOG.json! This meant we were in many occasions just pushing the entire file again and again, which could be 10s of MBs per file in some cases, and you can imagine in a repo our size, how that would be a problem.
but wouldn’t these erroneous diffs not show up in git diff
? it seems that they were pushing (maybe automatically?)without inspecting the diffs first
maybe I’m missing something but wouldn’t this show up in a diff before pushing?
thank you for your work. although i don’t post here i really appreciate the community and the work that involves. thanks a lot
simple vinaigrette. Olive oil, French mustard, vinegar, salt, pepper (garlic, shallots). depending on the salad it’s wine vinegar (red or white) or apple cider vinegar, Dijon or à l’ancienne mustard. if i feel fancy I’ll add some herbs (tarragon is great) or some egg yolk for extra creaminess.
this is my impression. back when i still was in academia it would pop up from time to time but i never published there since i never cited any of their journals in the first place. (why would one publish there when all your peers are somewhere else). nowadays i sometimes get requests from them to my personal email for special issues which i just ignore. (it’s academic spam essentially).
have a look at retraction watch https://retractionwatch.com/?s=mdpi