From: Theodore Tso <tytso@mit.edu>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
George Spelvin <linux@horizon.com>,
gitster@pobox.com, git@vger.kernel.org
Subject: Re: receive.denyCurrentBranch
Date: Mon, 9 Feb 2009 00:06:59 -0500 [thread overview]
Message-ID: <20090209050659.GA12655@mini-me.lan> (raw)
In-Reply-To: <76718490902081747s7a1ebe12yaf08665429a594c6@mail.gmail.com>
On Sun, Feb 08, 2009 at 08:47:26PM -0500, Jay Soffian wrote:
> I agree that a detached HEAD is a bad idea. The closest parallel that
> I can come up with for git would be for receive-pack to store incoming
> changes into separate branch hierarchy, NOT for it to detach HEAD. A
> toy-patch I played around with earlier allowed this on the non-bare
> upstream repo:
>
> [receive]
> prefix = refs/remotes/incoming
>
> Then a push to refs/heads/master was automatically stored as
> refs/remotes/incoming/master instead.
What happens when the next person pushes to the same remote repo, and
their refs/heads/master push is not a fast-forward merge of the
current refs/remotes/incoming/master?
Do you lose the first user's push at that point? Or do you refuse the
push?
- Ted
next prev parent reply other threads:[~2009-02-09 5:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 4:29 receive.denyCurrentBranch George Spelvin
2009-02-08 6:43 ` receive.denyCurrentBranch Junio C Hamano
2009-02-08 10:30 ` receive.denyCurrentBranch Johannes Schindelin
2009-02-08 17:50 ` receive.denyCurrentBranch Jay Soffian
2009-02-08 20:54 ` receive.denyCurrentBranch Johannes Schindelin
2009-02-08 22:16 ` receive.denyCurrentBranch Jay Soffian
2009-02-08 22:51 ` receive.denyCurrentBranch Jay Soffian
2009-02-08 23:41 ` receive.denyCurrentBranch Johannes Schindelin
2009-02-09 1:38 ` receive.denyCurrentBranch Junio C Hamano
2009-02-09 1:47 ` receive.denyCurrentBranch Jay Soffian
2009-02-09 5:06 ` Theodore Tso [this message]
2009-02-09 11:06 ` receive.denyCurrentBranch Johannes Schindelin
2009-02-09 15:46 ` receive.denyCurrentBranch Jay Soffian
2009-02-09 15:43 ` receive.denyCurrentBranch Jay Soffian
2009-02-08 22:03 ` receive.denyCurrentBranch Jakub Narebski
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=20090209050659.GA12655@mini-me.lan \
--to=tytso@mit.edu \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
--cc=linux@horizon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.