Re: [Savannah-users] Allowing non-fastforward pushes in git

[Bob Proulx]

Nik Nyby wrote:
> Kaz Kylheku <address@hidden> writes:
> > Git is crippled without non-fast-forward pushes. It means that the
> > repository is useless for doing development tasks, like rebasing a
> > topic development branch to the latest trunk. (An action that is
> > easily coordinated among developers.)

Saying it is useless is much too harsh.

> I agree - Please leave the LibreJS repository as non-fast-forward
> enabled. In the future I'll likely be needing to rebase topic branches
> onto the master branch, then force-pushing them. It's also required for
> squashing commits on topic branches into more logical parts, and
> re-pushing the revised topic branch.
> 
> If there's a mechanism that prevents the master branch from being
> force-pushed, rewriting the history of that branch, I'd be fine with
> enabling that. It's only a rare circumstance (like the reason I began
> this thread) that I would need to push non-fast-forward commits to the
> master branch.

I agree that the non-master branches should have this allowed.  Such
as for the typical use of the 'next' and 'pu' type of branches and for
other topic branches.  I will set something up in the hook scripts to
allow this.  Unfortunately I don't have an already written hook
script.  But I know what is needed and will find something or cook
something up for this.

Bob