From: Jay Soffian <jaysoffian@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Theodore Tso <tytso@mit.edu>, George Spelvin <linux@horizon.com>,
gitster@pobox.com, git@vger.kernel.org
Subject: Re: receive.denyCurrentBranch
Date: Mon, 9 Feb 2009 10:46:15 -0500 [thread overview]
Message-ID: <76718490902090746x49e06f54sa409eacf1078ddca@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0902091204100.10279@pacific.mpi-cbg.de>
On Mon, Feb 9, 2009 at 6:06 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>
> On Mon, 9 Feb 2009, Theodore Tso wrote:
>>
>>
>> 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?
>
> This is meant for non-bare repositories, right? Repositories that do have
> reflogs...
Absolutely. It would be insane on a bare repository.
> P.S.: There _have_ been times when I would have liked an automatic
> PUSH_HEAD that is always temporary, such as FETCH_HEAD. I _could_ imagine
> that this is something we could do (opt-in, of course): storing what was
> already pushed in a PUSH_HEAD, even if the refs could not be updated.
Oooh. Interesting idea.
j.
next prev parent reply other threads:[~2009-02-09 15:47 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 ` receive.denyCurrentBranch Theodore Tso
2009-02-09 11:06 ` receive.denyCurrentBranch Johannes Schindelin
2009-02-09 15:46 ` Jay Soffian [this message]
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=76718490902090746x49e06f54sa409eacf1078ddca@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux@horizon.com \
--cc=tytso@mit.edu \
/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).