From e5a56f2d50ce1939eba4fddbeb9c8e032db4fc95 Mon Sep 17 00:00:00 2001 From: Alexander Lanin Date: Fri, 3 Jan 2020 14:13:40 -0500 Subject: [PATCH] Remove outdated svn/git information from hacking page The patch files section is redundant to https://llvm.org/docs/GettingStarted.html. There is nothing clang specific here. We are talking about a monorepo after all. While it may seem nice to have one single clang page which explains everything, it's not: It doesn't cover the topics in sufficient depth, it's redundant to other pages and it's hard to keep it up to date as we see with the svn instructions. --- clang/www/hacking.html | 26 ++------------------------ 1 file changed, 2 insertions(+), 24 deletions(-) diff --git a/clang/www/hacking.html b/clang/www/hacking.html index fbcf88b..3623b90 100755 --- a/clang/www/hacking.html +++ b/clang/www/hacking.html @@ -275,30 +275,8 @@ Testing Time: 81.52s

Creating Patch Files

-

To return changes to the Clang team, unless you have checkin - privileges, the preferred way is to send patch files - using LLVM's Phabricator with an explanation of what the patch is for. Clang follows LLVM's developer policy. - If your patch requires a wider discussion (for example, because it is an - architectural change), you can use the cfe-dev mailing list.

- -

To create these patch files, change directory - to the llvm/tools/clang root and run:

- - 
svn diff (relative path) >(patch file name)
- -

For example, for getting the diffs of all of clang:

- - 
svn diff . >~/mypatchfile.patch
- -

For example, for getting the diffs of a single file:

- - 
svn diff lib/Parse/ParseDeclCXX.cpp >~/ParseDeclCXX.patch
- -

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.

- -

It is also possible to use git to contribute to Clang.

+

To contribute changes to Clang see + LLVM's Getting Started page

LLVM IR Generation

-- 2.7.4