[GNUnet-SVN] [gnurl] 116/163: include/README: remove "hacking" advice, not the right place

[gnunet]

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to branch master
in repository gnurl.

commit 13120f28b309e6276690383b2daa977ec9aa99c8
Author: Daniel Stenberg <address@hidden>
AuthorDate: Mon Jun 25 15:01:12 2018 +0200

    include/README: remove "hacking" advice, not the right place
---
 include/README | 19 ++-----------------
 1 file changed, 2 insertions(+), 17 deletions(-)

diff --git a/include/README b/include/README
index c2589ec8c..091ef76d1 100644
--- a/include/README
+++ b/include/README
@@ -14,20 +14,5 @@ of environment. You must include files from here using...
 ... style and point the compiler's include path to the directory holding the
 curl subdirectory. It makes it more likely to survive future modifications.
 
-NOTE FOR LIBCURL HACKERS
-
-* If you check out from git on a non-configure platform, you must run the
-  appropriate buildconf* script to set up files before being able of compiling
-  the library.
-
-* We cannot assume anything else but very basic compiler features being
-  present. While libcurl requires an ANSI C compiler to build, some of the
-  earlier ANSI compilers clearly can't deal with some preprocessor operators.
-
-* Newlines must remain unix-style for older compilers' sake.
-
-* Comments must be written in the old-style /* unnested C-fashion */
-
-To figure out how to do good and portable checks for features, operating
-systems or specific hardwarare, a very good resource is Bjorn Reese's
-collection at https://sourceforge.net/p/predef/wiki/
+The public curl include files can be shared freely between different platforms
+and different architectures.

-- 
To stop receiving notification emails like this one, please contact
address@hidden