On 04/02/2013 09:21 AM, David Henningsson wrote:
On 03/30/2013 07:00 AM, Tanu Kaskinen wrote:
I'm well aware of the -f flag. That paragraph you quoted talks about the
default behavior. The next paragraph tells how to change the default
behavior
with denyNonFastForwards, so that also forced pushe
On 03/30/2013 07:00 AM, Tanu Kaskinen wrote:
On Saturday, March 30, 2013 07:16:36 AM David Henningsson wrote:
On 03/29/2013 12:26 PM, Tanu Kaskinen wrote:
Hi,
I tried to rebase the next branch on master, but pushing a
non-fast-forward update failed, because the receive.denyNonFastforwards
opti
On Saturday, March 30, 2013 07:16:36 AM David Henningsson wrote:
> On 03/29/2013 12:26 PM, Tanu Kaskinen wrote:
> > Hi,
> >
> > I tried to rebase the next branch on master, but pushing a
> > non-fast-forward update failed, because the receive.denyNonFastforwards
> > option is set to true. If there
On 03/29/2013 12:26 PM, Tanu Kaskinen wrote:
Hi,
I tried to rebase the next branch on master, but pushing a non-fast-forward
update failed, because the receive.denyNonFastforwards option is set to true.
If there are no objections, I'll soon remove that option and replace it with
an update hook t
Hi,
I tried to rebase the next branch on master, but pushing a non-fast-forward
update failed, because the receive.denyNonFastforwards option is set to true.
If there are no objections, I'll soon remove that option and replace it with
an update hook that will by default reject non-fast-forward
