Re: [ANNOUNCE] Git v1.8.2-rc0

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Feb 18, 2013, 18:35 UTC
Message-ID: <vpq4nh9v5an.fsf@grenoble-inp.fr>
In-Reply-To: <7vk3q6e94s.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 13 quoted lines

> Git v1.8.2 Release Notes (draft)
> ========================
>
> Backward compatibility notes
> ----------------------------
>
> In the upcoming major release (tentatively called 1.8.2), we will
> change the behavior of the "git push" command.
>
> When "git push [$there]" does not say what to push, we have used the
> traditional "matching" semantics so far (all your branches were sent
> to the remote as long as there already are branches of the same name
> over there).  We will use the "simple" semantics

I don't understand: wasn't this supposed to happen in Git 2.0? Did you mean "In the upcoming major release (tentatively called *2.0*)"?

Also, you may want to mention the argumentless "git add -u" change too. It currently has an item below, but this is a future backward-incompatible change so it may deserve to appear in this section too.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/