Re: [ANNOUNCE] GIT 1.6.3

From
Sitaram Chamarty <hidden>
Date
2016-06-15 22:46:43
Reply to
Jeff Brown, 2016-06-15
On 2009-05-07, Jeff Brown [off-list ref] wrote:
On Thu, May 7, 2009 at 2:09 AM, Junio C Hamano [off-list ref] wrote:
quoted
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
Thread (3 messages) 3 messages, 3 authors, last reply 2016-06-15
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help