Re: Patch queue management systems

[David Kastrup]

Andreas Schwab <address@hidden> writes:

> David Kastrup <address@hidden> writes:
>
>> Doesn't need a separate repo: a server side commit hook refusing
>> non-fast-forward pushes (more exactly: updating the reference after the
>> commit object is already there) on any path not starting, say, with
>> dev/, should be easily possible.
>
> Doesn't even need that as long as you can delete branches.

Yes and no.  Deleting and recreating a branch removes its reflog.  If
something goes wrong at the server side, it might be nice to have
around.  For basically ephemeral branches, this might be fine.  For
branches like master, one might want to disable branch deletion
altogether except for possibly some privileged users.  For, say,
/dev/username/* one might want to restrict branch
deletion/non-fastforward to the given username.

A commit hook can do such things IIRC.

-- 
David Kastrup