git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Vajna <vmiklos@frugalware.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 1/2] Introduce receive.guardCurrentBranch
Date: Mon, 24 Mar 2008 02:21:39 +0100	[thread overview]
Message-ID: <20080324012139.GV14567@genesis.frugalware.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0803232142460.4353@racer.site>

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

On Sun, Mar 23, 2008 at 09:43:43PM +0100, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> +receive.guardCurrentBranch::
> +	If set to true, git-receive-pack will deny to update the ref that
> +	HEAD points to, if HEAD is not detached.  This configuration
> +	variable is set when initializing a non-bare repository.

probably i want too much, but it would be really nice if receive-pack
could just make HEAD detached. so that the user later can do a 'git
checkout -m master' to resolve possible conflicts.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-03-24  1:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23 20:43 [PATCH 1/2] Introduce receive.guardCurrentBranch Johannes Schindelin
2008-03-23 20:44 ` [PATCH 2/2] git-init: set receive.guardCurrentBranch = true for non-bare repositories Johannes Schindelin
2008-03-24  0:24   ` Junio C Hamano
2008-03-24 11:00     ` Johannes Schindelin
2008-03-24 16:50       ` Junio C Hamano
2008-03-24 17:10         ` Johannes Schindelin
2008-03-24 22:08           ` Daniel Barkalow
2008-03-24 22:31             ` Johannes Schindelin
2008-03-24  1:21 ` Miklos Vajna [this message]
2008-03-24 11:01   ` [PATCH 1/2] Introduce receive.guardCurrentBranch Johannes Schindelin
2008-03-24 14:10     ` Miklos Vajna

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=20080324012139.GV14567@genesis.frugalware.org \
    --to=vmiklos@frugalware.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).