[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Patch queue management systems

From: David Kastrup
Subject: Re: Patch queue management systems
Date: Thu, 11 Dec 2014 16:19:17 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]