git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [ANNOUNCE] GIT 1.6.3

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
May 7, 2009, 17:39 UTC
Message-ID
<slrnh0677a.at.sitaramc@sitaramc.homelinux.net>
In-Reply-To
<bbd12f0f0905070758q697f11fck259db4a0207d0aa7@mail.gmail.com>
On 2009-05-07, Jeff Brown <jeff@jeffandbetsy.net> wrote:
Show 11 quoted lines
> On Thu, May 7, 2009 at 2:09 AM, Junio C Hamano <gitster@pobox.com> wrote:
>>
>> With the next major release, "git push" into a branch that is
>> currently checked out will be refused by default.  You can choose
>> what should happen upon such a push by setting the configuration
>> variable receive.denyCurrentBranch in the receiving repository.
>>
>
> I want to make sure I understand how this will work.  Could you
> describe the simplest set of steps necessary to get into this
> situation where the push would be refused?

Most common scenario, happens often on irc, is you clone repo A to repo B, make some changes, and push. If all the defaults (simplest case) are used repo A has "master" checked out, and repo B then tries to push to that same (checked out) branch.

So:
    mkdir A; cd A; git init; make-some-commits
    cd ..;git clone A B;cd B; make-some-other-commits
    # and then
    git push    # from master on B to master on A
Previous: Jeff Brown
Message 3 of 3 in “[ANNOUNCE] GIT 1.6.3”
  1. Junio C HamanoMay 7, 2009
  2. Jeff BrownMay 7, 2009
  3. Sitaram ChamartyMay 7, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.