linux-kernel - Re: [ANNOUNCE] Git v1.8.2-rc0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <vpq4nh9v5an.fsf@grenoble-inp.fr>
Date:	Mon, 18 Feb 2013 19:35:28 +0100
From:	Matthieu Moy <Matthieu.Moy@...noble-inp.fr>
To:	Junio C Hamano <gitster@...ox.com>
Cc:	git@...r.kernel.org, Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [ANNOUNCE] Git v1.8.2-rc0

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

> 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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/