[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:26:21 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
Ted Zlatanov <address@hidden> writes:
> On Thu, 11 Dec 2014 15:55:35 +0100 Andreas Schwab <address@hidden> wrote:
>
> AS> 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.
>
> AS> Doesn't even need that as long as you can delete branches.
>
> Doesn't even need that as long as we have Github.
We don't "have" GitHub. It's owned by a company and is running
proprietary software to which we don't have access.
--
David Kastrup
- Re: Patch queue management systems, (continued)
- Re: Patch queue management systems, Dmitry Gutov, 2014/12/09
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/10
- Re: Patch queue management systems, Steinar Bang, 2014/12/11
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/11
- Re: Patch queue management systems, Steinar Bang, 2014/12/11
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/11
- Re: Patch queue management systems, David Kastrup, 2014/12/11
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/11
- Re: Patch queue management systems, Andreas Schwab, 2014/12/11
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/11
- Re: Patch queue management systems,
David Kastrup <=
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/11
- Re: Patch queue management systems, David Kastrup, 2014/12/11
- Re: Patch queue management systems, David Kastrup, 2014/12/11
- Re: Patch queue management systems, Achim Gratz, 2014/12/11