diff options
| author | Douglas Gregor <dgregor@apple.com> | 2011-11-19 19:14:26 +0000 |
|---|---|---|
| committer | Douglas Gregor <dgregor@apple.com> | 2011-11-19 19:14:26 +0000 |
| commit | 8b06d6b95b133822b5ac6a382843c39a689569b4 (patch) | |
| tree | 05769d24112d61e5b365124dadedad7a3fd4f7ed | |
| parent | 22c107b2b99887b5aec6d1fd38210031e944e31f (diff) | |
Tweak the guidelines for when one should send patches to cfe-commits vs. cfe-dev
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@145000 91177308-0d34-0410-b5e6-96231b3b80d8
| -rw-r--r-- | www/hacking.html | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/www/hacking.html b/www/hacking.html index bedb2b6a58..eef9d82816 100644 --- a/www/hacking.html +++ b/www/hacking.html @@ -255,11 +255,10 @@ Testing Time: 81.52s <p>To return changes to the Clang team, unless you have checkin privileges, the preferred way is to send patch files to the - cfe-commits mailing list, with an explanation of what the patch is for. - Or, if you have questions, or want to have a wider discussion of what - you are doing, such as if you are new to Clang development, you can use - the cfe-dev mailing list also. - </p> + cfe-commits mailing list, with an explanation of what the patch is + for. 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> |