From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: <gdb-patches@sourceware.org>
Cc: Stan Shebs <stan@codesourcery.com>
Subject: [PATCH] CONTRIBUTE: For internals refer to wiki, not gdb/doc
Date: Tue, 02 Sep 2014 16:30:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1409020252590.2958@tp.orcam.me.uk> (raw)
Hi,
I've noticed that after this change:
commit 0a7cfe2cf50b450d0cf9db16ee4bd027e08763e8
Author: Stan Shebs <shebs@codesourcery.com>
Date: Mon Sep 16 18:00:34 2013 +0000
we've now got a stale reference in gdb/CONTRIBUTE to our former internals
documentation in gdb/doc. Let's fix it up. OK to apply?
2014-09-02 Maciej W. Rozycki <macro@codesourcery.com>
gdb/
* CONTRIBUTE (Coding Standards): For internals refer to wiki,
not gdb/doc.
Maciej
gdb-contrib-gdbint.diff
Index: gdb-fsf-trunk-quilt/gdb/CONTRIBUTE
===================================================================
--- gdb-fsf-trunk-quilt.orig/gdb/CONTRIBUTE 2013-10-26 20:23:01.000000000 +0100
+++ gdb-fsf-trunk-quilt/gdb/CONTRIBUTE 2014-09-01 17:58:42.068940061 +0100
@@ -32,11 +32,12 @@ o Coding Standards
Submissions which do not conform to the standards will be
returned with a request to reformat the changes.
+ Ref: http://www.gnu.org/prep/standards_toc.html
+
GDB has certain additional coding requirements. Those
- requirements are explained in the GDB internals documentation
- in the gdb/doc directory.
+ requirements are explained in the GDB internals documentation.
- Ref: http://www.gnu.org/prep/standards_toc.html
+ Ref: http://sourceware.org/gdb/wiki/Internals%20Coding-Standards
o Copyright Assignment
next reply other threads:[~2014-09-02 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 16:30 Maciej W. Rozycki [this message]
2014-09-02 16:37 ` Sergio Durigan Junior
2014-09-02 17:11 ` Maciej W. Rozycki
2014-09-09 16:49 ` [PING][PATCH] " Maciej W. Rozycki
2014-09-16 22:49 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.1409020252590.2958@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox