From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Sam Vilain <sam@vilain.net>
Subject: [RFC PATCH 0/4] deny push to current branch of non-bare repo
Date: Fri, 7 Nov 2008 17:07:30 -0500 [thread overview]
Message-ID: <20081107220730.GA15942@coredump.intra.peff.net> (raw)
The short of it is that it's dangerous, we see people confused by it
(there was another one just yesterday), and it's a FAQ:
http://git.or.cz/gitwiki/GitFaq#head-b96f48bc9c925074be9f95c0fce69bcece5f6e73
The FAQ even says "don't do this until you know what you are doing." So
the safety valve is configurable, so that those who know what they are
doing can switch it off.
And it's even on Sam's "UI improvements" list. :)
Patch 4/4 is the interesting one. 1/4 is a cleanup I saw while fixing
tests. 2/4 is a cleanup to prepare for 3/4. And 3/4 fixes a bunch of
tests which were inadvertently doing such a push (but didn't care
because they didn't look at the working directory).
-Peff
next reply other threads:[~2008-11-07 22:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 22:07 Jeff King [this message]
2008-11-07 22:09 ` [PATCH 1/4] t5400: expect success for denying deletion Jeff King
2008-11-09 10:38 ` Jan Krüger
2008-11-07 22:20 ` [PATCH 2/4] t5516: refactor oddball tests Jeff King
2008-11-07 22:22 ` [PATCH 3/4] tests: avoid pushing to current branch of non-bare repo Jeff King
2008-11-07 22:28 ` [PATCH 4/4] receive-pack: deny push " Jeff King
2008-11-07 22:39 ` [RFC PATCH 0/4] " Mark Burton
2008-11-07 23:16 ` Junio C Hamano
2008-11-08 14:27 ` Jeff King
2008-11-08 15:12 ` Johannes Schindelin
2008-11-08 20:49 ` Junio C Hamano
2008-11-09 1:49 ` Jeff King
2008-11-09 22:12 ` Junio C Hamano
2008-11-12 0:44 ` Kyle Moffett
2008-11-12 8:44 ` Jeff King
2008-11-13 5:22 ` Kyle Moffett
2008-11-13 5:37 ` Jeff King
2008-11-13 6:14 ` Junio C Hamano
2008-11-13 13:58 ` Kyle Moffett
2008-11-14 6:37 ` Jeff King
2008-12-02 2:22 ` Leo Razoumov
2008-12-02 2:29 ` Junio C Hamano
2008-12-02 2:41 ` Leo Razoumov
2008-12-02 2:48 ` Jeff King
2008-12-02 3:08 ` Leo Razoumov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081107220730.GA15942@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sam@vilain.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).