From: Diego Novillo <dnovillo@redhat.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Daniel Franke <franke.daniel@gmail.com>,
gerald@pfeifer.com, gcc-patches@gcc.gnu.org
Subject: Re: [patch, libgomp, docs] adding documentation to libgomp
Date: Thu, 21 Dec 2006 21:58:00 -0000 [thread overview]
Message-ID: <458B0370.4040800@redhat.com> (raw)
In-Reply-To: <4aca3dc20612101758y2438d4afu1a789c2b1c134034@mail.gmail.com>
Daniel Berlin wrote on 12/10/06 20:58:
> Diego, just an FYI, I believe you can approve patches to docs that are
> for area you maintain.
>
> Or is it that we just are allowed to modify them.
>
> Gerald, can you clarify (and review this kind person's texinfo formatting)?
>
Daniel just pointed out to me this paragraph from
http://gcc.gnu.org/svnwrite.html
"Maintainers of a port maintain the files in config/port/, the configure
fragments for the port, documentation for the port and test cases for
^^^^^^^^^^^^^^^^^^^^^^^^^^
features or bugs specific to this port. Port maintainers do not have
approval rights in other files."
I think that solves the issue. Daniel, your patch is fine. If I
overstepped any boundaries, maybe we should clarify this a bit more.
next prev parent reply other threads:[~2006-12-21 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 23:40 Daniel Franke
2006-11-28 23:42 ` Diego Novillo
2006-11-29 9:59 ` Daniel Franke
2006-11-29 12:22 ` Diego Novillo
2006-11-30 21:02 ` Daniel Franke
2006-12-10 21:52 ` Daniel Franke
2006-12-11 1:58 ` Daniel Berlin
2006-12-11 13:20 ` Diego Novillo
2006-12-17 20:40 ` Daniel Franke
2006-12-21 21:58 ` Diego Novillo [this message]
2007-01-07 0:19 ` Gerald Pfeifer
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=458B0370.4040800@redhat.com \
--to=dnovillo@redhat.com \
--cc=dberlin@dberlin.org \
--cc=franke.daniel@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).