Re: [PATCH v3 1/1] Add another option for receive.denyCurrentBranch

2014-11-13 Thread Johannes Schindelin
Hi Junio, On Thu, 13 Nov 2014, Junio C Hamano wrote: > Johannes Schindelin writes: > > > diff --git a/t/t5516-fetch-push.sh b/t/t5516-fetch-push.sh > > index f4da20a..ba002a9 100755 > > --- a/t/t5516-fetch-push.sh > > +++ b/t/t5516-fetch-push.sh > > @@ -1330,4 +1330,21 @@ test_expect_success 'f

Re: [PATCH v3 1/1] Add another option for receive.denyCurrentBranch

2014-11-13 Thread Junio C Hamano
Johannes Schindelin writes: > diff --git a/t/t5516-fetch-push.sh b/t/t5516-fetch-push.sh > index f4da20a..ba002a9 100755 > --- a/t/t5516-fetch-push.sh > +++ b/t/t5516-fetch-push.sh > @@ -1330,4 +1330,21 @@ test_expect_success 'fetch into bare respects > core.logallrefupdates' ' > ) > ' >

[PATCH v3 1/1] Add another option for receive.denyCurrentBranch

2014-11-13 Thread Johannes Schindelin
When synchronizing between working directories, it can be handy to update the current branch via 'push' rather than 'pull', e.g. when pushing a fix from inside a VM, or when pushing a fix made on a user's machine (where the developer is not at liberty to install an ssh daemon let alone know the use