| 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
| ||
|
Message-ID: <vpqprhte3rs.fsf@bauges.imag.fr> Date: Sun, 08 Feb 2009 09:23:03 +0100 From: Matthieu Moy <Matthieu.Moy@...g.fr> To: Junio C Hamano <gitster@...ox.com> Cc: git@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [ANNOUNCE] GIT 1.6.2-rc0 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. There's probably a better wording, but what about ---- 8< --- With the next major release, "git push" into a branch that is currently checked out will be refused by default: Pushing to a checked-out branch changes the HEAD for this branch, and would confuse further local operations in the target repository. You can choose what should happen [...] ---- 8< --- ? -- Matthieu -- 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/
Powered by blists - more mailing lists