<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 20, 2019 at 6:25 PM Kristina Brooks via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org">cfe-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">Excuse my ignorance (I'm not great with Git) but how would it differ for workflows of people<br>
who use a Git repository for local work but still use `svn up + patch + svn commit <list of<br>
files>` to actually land post CR or for NFC patches, while resolving conflicts during a<br>
pull into a local (non-trunk) branch manually, after the eventual full switch to GitHub?<br></blockquote><div>I think SVN does not factor at all into where this thread is going: This is about what happens after the switch.<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">
<br>
I'm aware that SVN operates using the lock model as opposed to Git essentially making the<br>
history linear; Are merge commits multiple commits that are landed as part of a single<br>
Git "push" (ie. unsquashed), or attempts to do anything that would result in a creation<br>
or merging of a branch on the remote?<br></blockquote><div>Git history is not inherently linear. Merge commits are where different branches of development are merged together. Instead of merging different branches together (and retaining the history of the branches), it is possible to chose one as the "base" branch and "rebase" the other onto that branch. The Git history then appears to be linear.<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">
<br>
Thank you.<br>
<br>
On 3/20/2019 6:53 PM, Tom Stellard via llvm-dev wrote:<br>
> On 03/20/2019 11:38 AM, Zachary Turner wrote:<br>
>> It sounds like we need to get someone from the Foundation (chandlerc@, lattner@, tanya@, someone else?) to reach out to them offline about this.<br>
>><br>
> <br>
> Yes, we will try to reach out to GitHub directly about this, but I still<br>
> think we need some kind of contingency plan in case pre-receive hooks<br>
> or even a new kind of branch protection won't be an option for us.<br>
> <br>
> -Tom<br>
> <br>
>> On Wed, Mar 20, 2019 at 11:23 AM Arthur O'Dwyer <<a href="mailto:arthur.j.odwyer@gmail.com" target="_blank">arthur.j.odwyer@gmail.com</a> <mailto:<a href="mailto:arthur.j.odwyer@gmail.com" target="_blank">arthur.j.odwyer@gmail.com</a>>> wrote:<br>
>><br>
>> On Wed, Mar 20, 2019 at 2:19 PM Tom Stellard via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a> <mailto:<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>>> wrote:<br>
>><br>
>> On 03/20/2019 10:41 AM, Zachary Turner wrote:<br>
>> ><br>
>> > On Tue, Mar 19, 2019 at 12:00 PM Tom Stellard via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a> <mailto:<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>> <mailto:<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a> <mailto:<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>>>> wrote:<br>
>> ><br>
>> > Hi,<br>
>> ><br>
>> > I would like to follow up on the previous thread[1], where there was a consensus<br>
>> > to disallow merge commits in the llvm github repository, and start a discussion<br>
>> > about how we should enforce this policy.<br>
>> ><br>
>> > Unfortunately, GitHub does not provide a convenient way to fully enforce this policy.<br>
>> ><br>
>> > <br>
>> > Why isn't this enforceable with a server-side pre-receive hook?<br>
>><br>
>> GitHub[1] only supports pre-receive hooks in the 'Enterprise Server'<br>
>> plan, which is for self-hosted github instances.<br>
>><br>
>><br>
>> AIUI, the GitHub team is perfectly willing to help out the LLVM project in whatever way LLVM needs, including but not limited to turning on server-side hooks for us.<br>
>> <a href="https://twitter.com/natfriedman/status/1086470665832607746" rel="noreferrer" target="_blank">https://twitter.com/natfriedman/status/1086470665832607746</a><br>
>><br>
>> Server-side hooks are *the *answer to this problem. There is no problem. You just use a server-side hook.<br>
>><br>
>> (Whether or not to use GitHub PRs is an orthogonal question. You can use hooks with PRs, or hooks without PRs; PRs with hooks, or PRs without hooks.)<br>
>><br>
>> –Arthur<br>
>><br>
> <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>
> <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>
</blockquote></div></div>