summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDouglas Gregor <dgregor@apple.com>2011-11-19 19:14:26 +0000
committerDouglas Gregor <dgregor@apple.com>2011-11-19 19:14:26 +0000
commit328d8d255ed7fed38a499fdd0acfe6cf7f524d65 (patch)
tree9b2c46a376c5e88de13b5af6c80102b62444779d
parent3af6ae089f6dbd55fa8762227ef98fcbaf29050a (diff)
downloadbcm5719-llvm-328d8d255ed7fed38a499fdd0acfe6cf7f524d65.tar.gz
bcm5719-llvm-328d8d255ed7fed38a499fdd0acfe6cf7f524d65.zip
Tweak the guidelines for when one should send patches to cfe-commits vs. cfe-dev
llvm-svn: 145000
-rw-r--r--clang/www/hacking.html9
1 files changed, 4 insertions, 5 deletions
diff --git a/clang/www/hacking.html b/clang/www/hacking.html
index bedb2b6a588..eef9d82816a 100644
--- a/clang/www/hacking.html
+++ b/clang/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>
OpenPOWER on IntegriCloud