Re: [PATCH] Switch receive.denyCurrentBranch to "refuse"
- From
Asheesh Laroia <asheesh@asheesh.org>
- Date
- Jan 30, 2009, 01:32 UTC
- Message-ID
- <alpine.DEB.2.00.0901291729540.22558@vellum.laroia.net>
- In-Reply-To
- <alpine.DEB.1.00.0901300133070.3586@pacific.mpi-cbg.de>
On Fri, 30 Jan 2009, Johannes Schindelin wrote:
Show 9 quoted lines
> case DENY_REFUSE:
> - if (!is_ref_checked_out(name))
> + if (is_bare_repository() || !is_ref_checked_out(name))
> break;
> - error("refusing to update checked out branch: %s", name);
> + error("refusing to update checked out branch: %s\n"
> + "if you know what you are doing, you can allow it by "
> + "setting\n\n"
> + "\tgit config receive.denyCurrentBranch true\n", name);It seems like those new users you're trying to protect could use an additional sentence, like:
"A bare repository would not have this issue."
or
"You may prefer to have a bare repository instead."
Being told how to do it right is even better than being told that you're doing it wrong. (-:
-- Asheesh.
-- Fame is a vapor; popularity an accident; the only earthly certainty is oblivion. -- Mark Twain