Re: [PATCH v3] push --force-with-lease: Fix ref status reporting

2016-01-29 Thread Andrew Wheeler
> These all look OK (I am not sure about message i18n, though). > > Do we not test a case where --force-with-lease push is rejected due > to REF_STATUS_REJECT_STALE? Good idea, new patch on the way. -andrew -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a messag

Re: [PATCH v3] push --force-with-lease: Fix ref status reporting

2016-01-28 Thread Junio C Hamano
Andrew Wheeler writes: > diff --git a/t/t5533-push-cas.sh b/t/t5533-push-cas.sh > index c402d8d..c65033f 100755 > --- a/t/t5533-push-cas.sh > +++ b/t/t5533-push-cas.sh > @@ -101,7 +101,8 @@ test_expect_success 'push to update (allowed, tracking)' ' > ( > cd dst && >

[PATCH v3] push --force-with-lease: Fix ref status reporting

2016-01-28 Thread Andrew Wheeler
From: Andrew Wheeler The --force--with-lease push option leads to less detailed status information than --force. In particular, the output indicates that a reference was fast-forwarded, even when it was force-updated. Modify the --force-with-lease ref status logic to leverage the --force ref sta