<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">That somewhat depends. If the patch is relating to swift support, it should go through GitHub. If the patch is more general to LLDB we are encouraging contributions to <a href="http://LLVM.org" class="">LLVM.org</a>, which would be Phabricator (<a href="http://reviews.llvm.org" class="">reviews.llvm.org</a>).<div class=""><br class=""></div><div class="">This is the same policy we use for LLVM, Clang and the other <a href="http://LLVM.org" class="">LLVM.org</a> projects.</div><div class=""><br class=""></div><div class="">-Chris</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 9, 2017, at 11:41 AM, Robert Widmann <<a href="mailto:devteam.codafi@gmail.com" class="">devteam.codafi@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Does this mean patches for LLDB-Swift will have to go through Phabricator instead of Github?</div><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class=""></div><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">~Robert Widmann</div><br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" class=""><div class="">On Feb 9, 2017, at 1:50 PM, Chris Bieneman via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hello Swift-Dev and Swift-LLDB-Dev,<div class=""><br class=""></div><div class="">Over the last couple weeks we’ve been working on some changes to the branch management strategy for the Swift-LLDB repository. The goal is to have LLDB more closely align with the other projects forked from<span class="Apple-converted-space"> </span><a href="http://llvm.org/" class="">LLVM.org</a>. We believe that making this change will simplify the contribution process for LLDB’s Swift support.</div><div class=""><br class=""></div><div class="">To this end, we are making the following changes:</div><div class=""><br class=""></div><div class="">LLDB has gained an upstream-with-trunk branch which will be auto-merged from<span class="Apple-converted-space"> </span><a href="http://llvm.org/" class="">LLVM.org</a>’s LLDB/trunk. This branch will contain the best of both worlds. The latest and greatest from<span class="Apple-converted-space"> </span><a href="http://llvm.org/" class="">LLVM.org</a>, and Swift support. This branch will pair to LLVM & Clang’s upstream-with-swift branches and Swift’s master-next.</div><div class=""><br class=""></div><div class="">LLDB has also gained a stable branch which will behave the same way as the LLVM & Clang stable branches, and should be used for most Swift compiler development. Additionally we have made the swift-lldb/stable branch the default branch on the GitHub repository, which matches the behavior of LLVM & Clang.</div><div class=""><br class=""></div><div class="">LLDB’s master and master-next branches will be going away. Later today we will lock the branches, and in a few days we’ll delete them. For most users you’ll want to migrate from Swift-LLDB/master to Swift-LLDB/stable.</div><div class=""><br class=""></div><div class="">The new branches are already created, and the tooling will be coming online over the next few days. Additionally, the Swift contributing page (<a href="https://swift.org/contributing/#llvm-and-swift" class="">https://swift.org/contributing/#llvm-and-swift</a>) has been updated to reflect the alignment of the LLDB process with the other<span class="Apple-converted-space"> </span><a href="http://llvm.org/" class="">LLVM.org</a> projects.</div><div class=""><br class=""></div><div class="">If you have any questions about the new process or the transition please let me know.</div><div class=""><br class=""></div><div class="">Thank you,</div><div class="">-Chris</div></div>_______________________________________________<br class="">swift-dev mailing list<br class=""><a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-dev" class="">https://lists.swift.org/mailman/listinfo/swift-dev</a></div></blockquote></div></div></blockquote></div><br class=""></div></body></html>