<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 17, 2019 at 11:17 AM Philip Reames via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>I'm also a strong proponent of not requiring the wrapper.</p>
<p>The linear history piece was important enough to make the cost
worth it. The extra branches piece really isn't. If someone
creates a branch that's not supposed to exist, we just delete it.
No big deal. It will happen, but the cost is so low I don't worry
about it. <br>
</p>
<p>There's a bunch of things in our developer policy we don't
enforce except through social means. I don't see any reason why
the "no branches" thing needs to be special. <br>
</p>
<p> If we really want some automation, a simple script that polls
for new branches every five minutes and deletes them unless on a
while list would work just fine. :)</p></div></blockquote><div><br>Yeah, that about sums up my feelings as well.<br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
<p>Philip<br>
</p>
<div>On 10/15/19 9:26 PM, Mehdi AMINI via
cfe-dev wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Oct 15, 2019 at
12:26 PM Hubert Tong via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Oct 15, 2019
at 3:47 AM Marcus Johnson via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I
say retire it instantly.<br>
</blockquote>
<div>+1. It has never been a real requirement to use the
script. Using native svn is still viable until the
point of the migration.<br>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>It was a requirement for the "linear history" feature.
With GitHub providing this now, I'm also +1 on retiring the
tool unless there is a another use that can be articulated
for it?</div>
<div><br>
</div>
<div>-- </div>
<div>Mehdi</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_quote">
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
> On Oct 15, 2019, at 3:14 AM, Tom Stellard via
cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>>
wrote:<br>
> <br>
> Hi,<br>
> <br>
> I mentioned this in my email last week, but I
wanted to start a new<br>
> thread to get everyone's input on what to do
about the git-llvm script<br>
> after the GitHub migration.<br>
> <br>
> The original plan was to require the use of the
git-llvm script when<br>
> committing to GitHub even after the migration was
complete.<br>
> The reason we decided to do this was so that we
could prevent developers<br>
> from accidentally pushing merge commits and
making the history non-linear.<br>
> <br>
> Just in the last week, the GitHub team completed
the "Require Linear<br>
> History" branch protection, which means we can
now enforce linear<br>
> history server side and do not need the git-llvm
script to do this.<br>
> <br>
> With this new development, the question I have is
when should the<br>
> git-llvm script become optional? Should we make
it optional immediately,<br>
> so that developers can push directly using
vanilla git from day 1, or should we<br>
> wait a few weeks/months until things have
stabilized to make it optional?<br>
> <br>
> Thanks,<br>
> Tom<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> cfe-dev mailing list<br>
> <a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
> <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote>
</div>
</div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
cfe-dev mailing list
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div></div>