linux-kernel - Re: [ANNOUNCE] GIT 1.6.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] [day] [month] [year] [list]

Message-ID: <7vvdrlz2jl.fsf@gitster.siamese.dyndns.org>
Date:	Sun, 08 Feb 2009 01:43:58 -0800
From:	Junio C Hamano <gitster@...ox.com>
To:	Matthieu Moy <Matthieu.Moy@...g.fr>
Cc:	git@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.6.2-rc0

Matthieu Moy <Matthieu.Moy@...g.fr> writes:

> Junio C Hamano <gitster@...ox.com> writes:
>
>> GIT v1.6.2 Release Notes (draft)
>> ================================
>>
>> With the next major release, "git push" into a branch that is
>> currently checked out will be refused by default.  You can choose
>> what should happen upon such a push by setting the configuration
>> variable receive.denyCurrentBranch in the receiving repository.
>
> Perhaps this paragraph should tell _why_ this is a dangerous
> operation.

I considered it, but that is not what Release Notes is about.  It should
be a table-of-contents of the highlights in the new release.  Interested
parties can look at the documentation for gory details.
--
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/