[SCM] GNU gnutls branch, master, updated. gnutls_2_99_1-22-g27a16a1

[Nikos Mavrogiannopoulos]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU gnutls".

http://git.savannah.gnu.org/cgit/gnutls.git/commit/?id=27a16a1b0f07bc02cc95f2210447e339f699fcbc

The branch, master has been updated
       via  27a16a1b0f07bc02cc95f2210447e339f699fcbc (commit)
      from  4d96eeea9944c5853c9a85244c1bfb7325e0569b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 27a16a1b0f07bc02cc95f2210447e339f699fcbc
Author: Nikos Mavrogiannopoulos <address@hidden>
Date:   Sun May 8 10:11:45 2011 +0200

    removed references that produced nothing in pdf.

-----------------------------------------------------------------------

Summary of changes:
 doc/cha-preface.texi |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/cha-preface.texi b/doc/cha-preface.texi
index 10e41d6..1b2d5a3 100644
--- a/doc/cha-preface.texi
+++ b/doc/cha-preface.texi
@@ -224,12 +224,13 @@ For code contributions, a number of style guides will 
help you:
 @itemize @bullet
 
 @item Coding Style.
-Follow the GNU Standards document (@pxref{top, GNU Coding Standards,,
-standards}).
+Follow the GNU Standards document.
address@hidden (@pxref{top, GNU Coding Standards,,standards}).
 
 If you normally code using another coding standard, there is no
 problem, but you should use @samp{indent} to reformat the code
-(@pxref{top, GNU Indent,, indent}) before submitting your work.
address@hidden (@pxref{top, GNU Indent,, indent}) 
+before submitting your work.
 
 @item Use the unified diff format @samp{diff -u}.
 


hooks/post-receive
-- 
GNU gnutls