Home » Mailing list archives » git » 2008 » November » 7

[RFC PATCH 0/4] deny push to current branch of non-bare repo

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Jeff King <peff@...>
To: <git@...>
Cc: Junio C Hamano <gitster@...>, Sam Vilain <sam@...>
Subject: [RFC PATCH 0/4] deny push to current branch of non-bare repo
Date: Friday, November 7, 2008 - 6:07 pm

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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
[RFC PATCH 0/4] deny push to current branch of non-bare repo, Jeff King, (Fri Nov 7, 6:07 pm)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Junio C Hamano, (Fri Nov 7, 7:16 pm)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Jeff King, (Sat Nov 8, 10:27 am)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Leo Razoumov, (Mon Dec 1, 10:22 pm)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Jeff King, (Mon Dec 1, 10:48 pm)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Leo Razoumov, (Mon Dec 1, 11:08 pm)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Junio C Hamano, (Mon Dec 1, 10:29 pm)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Leo Razoumov, (Mon Dec 1, 10:41 pm)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Junio C Hamano, (Sat Nov 8, 4:49 pm)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Jeff King, (Sat Nov 8, 9:49 pm)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Kyle Moffett, (Tue Nov 11, 8:44 pm)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Jeff King, (Wed Nov 12, 4:44 am)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Kyle Moffett, (Thu Nov 13, 1:22 am)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Jeff King, (Thu Nov 13, 1:37 am)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Junio C Hamano, (Thu Nov 13, 2:14 am)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Kyle Moffett, (Thu Nov 13, 9:58 am)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Jeff King, (Fri Nov 14, 2:37 am)
Re: [RFC PATCH 0/4] deny push to current branch of non-bare ..., Johannes Schindelin, (Sat Nov 8, 11:12 am)
[PATCH 4/4] receive-pack: deny push to current branch of non..., Jeff King, (Fri Nov 7, 6:28 pm)
[PATCH 3/4] tests: avoid pushing to current branch of non-ba..., Jeff King, (Fri Nov 7, 6:22 pm)
[PATCH 2/4] t5516: refactor oddball tests, Jeff King, (Fri Nov 7, 6:20 pm)
[PATCH 1/4] t5400: expect success for denying deletion, Jeff King, (Fri Nov 7, 6:09 pm)
Re: [PATCH 1/4] t5400: expect success for denying deletion, Jan , (Sun Nov 9, 6:38 am)