[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Work Branches
From:       Michael Reeves <reeves.87 () gmail ! com>
Date:       2019-10-05 15:25:52
Message-ID: CANp6eRm4t2UaZOcrQ4dggOYDnjxkeB6FOsULj-TbDjk44SY4rg () mail ! gmail ! com
[Download RAW message or body]

On Fri, Oct 4, 2019, 10:11 PM Ben Cooksley <bcooksley@kde.org> wrote:

> Hi all,
>
> Recently we had a discussion (which I think may have ended up spread
> over a couple of mailing lists in the end) concerning branches and the
> ability to force push to them.
>
> Current policy forbids force pushing to branches except in very
> limited circumstances (essentially where it is the only option to fix
> a branch)
>
> 2) Protect all branches, aside from a given prefix (proposed to be work/)
>

In view of the fact that other may also be working on the code this seems
best.

[Attachment #3 (text/html)]

<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Fri, Oct 4, 2019, 10:11 PM Ben Cooksley &lt;<a \
href="mailto:bcooksley@kde.org">bcooksley@kde.org</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi all,<br> <br>
Recently we had a discussion (which I think may have ended up spread<br>
over a couple of mailing lists in the end) concerning branches and the<br>
ability to force push to them.<br>
<br>
Current policy forbids force pushing to branches except in very<br>
limited circumstances (essentially where it is the only option to fix<br>
a branch)<br><br>
2) Protect all branches, aside from a given prefix (proposed to be \
work/)<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">In view \
of the fact that other may also be working on the code this seems best.</div><div \
dir="auto"><br></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]