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?

On Wed, Mar 14, 2012 at 9:29 PM, Junio C Hamano [off-list ref] wrote:

Dmitry Potapov [off-list ref] writes:

quoted

... 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?

Maybe not, but so far I have never had any problem with the way I use now.
So I have not had any real insensitive to change that. Though I agree that
what you proposed is better except pruning deleted branches.

It only shows that lack of "push --prune A" is a problem to be solved.

And hasn't it been solved already?

Has it? Somehow I cannot find the corresponding option in the manual.
What did I miss?

Dmitry