Re: [RFC PATCH] push: start warning upcoming default change for push.default

Dmitry Potapov [off-list ref] writes:

... However, if I do
"git push A ..." as you suggested then A will accumulate old garabage
from B very quickly.

That is not a valid excuse, is it?
It only shows that lack of "push --prune A" is a problem to be solved.

And hasn't it been solved already?