AlexanderLanin updated this revision to Diff 235968. AlexanderLanin retitled this revision from "[docs] Update dead anchor in hacking page" to "[docs] Remove outdated svn/git information from hacking page". AlexanderLanin edited the summary of this revision. AlexanderLanin added a comment.
Not sure we can call this updated proposal 'love': it's definitely not the goal to have less documentation, just less redundancy. I'll remove redundancies between those two in a separate pull request: - https://llvm.org/docs/Contributing.html#how-to-submit-a-patch - https://llvm.org/docs/GettingStarted.html#sending-patches CHANGES SINCE LAST ACTION https://reviews.llvm.org/D72057/new/ https://reviews.llvm.org/D72057 Files: clang/www/hacking.html Index: clang/www/hacking.html =================================================================== --- clang/www/hacking.html +++ clang/www/hacking.html @@ -275,30 +275,8 @@ <h2 id="patches">Creating Patch Files</h2> <!--=====================================================================--> - <p>To return changes to the Clang team, unless you have checkin - privileges, the preferred way is to send patch files - <a href="https://llvm.org/docs/Contributing.html#how-to-submit-a-patch";>using LLVM's Phabricator</a> with an explanation of what the patch is for. Clang follows <a - href="https://llvm.org/docs/DeveloperPolicy.html";>LLVM's developer policy</a>. - If your patch requires a wider discussion (for example, because it is an - architectural change), you can use the cfe-dev mailing list.</p> - - <p>To create these patch files, change directory - to the llvm/tools/clang root and run:</p> - - <pre>svn diff (relative path) >(patch file name)</pre> - - <p>For example, for getting the diffs of all of clang:</p> - - <pre>svn diff . >~/mypatchfile.patch</pre> - - <p>For example, for getting the diffs of a single file:</p> - - <pre>svn diff lib/Parse/ParseDeclCXX.cpp >~/ParseDeclCXX.patch</pre> - - <p>Note that the paths embedded in the patch depend on where you run it, - so changing directory to the llvm/tools/clang directory is recommended.</p> - - <p>It is also possible to <a href="https://llvm.org/docs/GettingStarted.html#sending-patches-with-git";>use git to contribute</a> to Clang.</p> + <p>To contribute changes to Clang see + <a href="https://llvm.org/docs/GettingStarted.html#sending-patches";>LLVM's Getting started page</a></p> <!--=====================================================================--> <h2 id="irgen">LLVM IR Generation</h2>
Index: clang/www/hacking.html =================================================================== --- clang/www/hacking.html +++ clang/www/hacking.html @@ -275,30 +275,8 @@ <h2 id="patches">Creating Patch Files</h2> <!--=====================================================================--> - <p>To return changes to the Clang team, unless you have checkin - privileges, the preferred way is to send patch files - <a href="https://llvm.org/docs/Contributing.html#how-to-submit-a-patch";>using LLVM's Phabricator</a> with an explanation of what the patch is for. Clang follows <a - href="https://llvm.org/docs/DeveloperPolicy.html";>LLVM's developer policy</a>. - If your patch requires a wider discussion (for example, because it is an - architectural change), you can use the cfe-dev mailing list.</p> - - <p>To create these patch files, change directory - to the llvm/tools/clang root and run:</p> - - <pre>svn diff (relative path) >(patch file name)</pre> - - <p>For example, for getting the diffs of all of clang:</p> - - <pre>svn diff . >~/mypatchfile.patch</pre> - - <p>For example, for getting the diffs of a single file:</p> - - <pre>svn diff lib/Parse/ParseDeclCXX.cpp >~/ParseDeclCXX.patch</pre> - - <p>Note that the paths embedded in the patch depend on where you run it, - so changing directory to the llvm/tools/clang directory is recommended.</p> - - <p>It is also possible to <a href="https://llvm.org/docs/GettingStarted.html#sending-patches-with-git";>use git to contribute</a> to Clang.</p> + <p>To contribute changes to Clang see + <a href="https://llvm.org/docs/GettingStarted.html#sending-patches";>LLVM's Getting started page</a></p> <!--=====================================================================--> <h2 id="irgen">LLVM IR Generation</h2>
_______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
