Re: [ANNOUNCE] GIT 1.6.3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2009-05-07, Jeff Brown <jeff@xxxxxxxxxxxxxxxx> wrote:
> On Thu, May 7, 2009 at 2:09 AM, Junio C Hamano <gitster@xxxxxxxxx> 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

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]