public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add support for embedding scripts in .debug_gdb_scripts.
Date: Fri, 13 Feb 2015 16:45:00 -0000	[thread overview]
Message-ID: <837fvl4v64.fsf@gnu.org> (raw)
In-Reply-To: <54DE2324.5030302@earthlink.net>

> Date: Fri, 13 Feb 2015 08:15:32 -0800
> From: Stan Shebs <stanshebs@earthlink.net>
> 
> In general, I would like to have the documentation maintainer be more of
> an editor, to have more of a free hand in deciding style rules, and to
> not insist that everything has to be written down beforehand.

I'm okay with that, but I'm also trying not to prevent contributors
from saying things their way.  Some people quite understandably feel
attached to what they wrote, so unnecessary changes risk causing
aggravation.

  reply	other threads:[~2015-02-13 16:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 17:32 Doug Evans
2015-01-15 18:11 ` Eli Zaretskii
2015-01-16 17:15   ` Doug Evans
2015-01-16 18:02     ` Eli Zaretskii
2015-01-17  1:16       ` Doug Evans
2015-01-17  8:16         ` Eli Zaretskii
2015-01-18  4:16           ` Doug Evans
2015-01-18 16:23             ` Eli Zaretskii
2015-01-18 20:48               ` Doug Evans
2015-01-19 14:49                 ` Joel Brobecker
2015-01-20 16:35                   ` Doug Evans
2015-01-21  9:57                     ` Joel Brobecker
2015-02-13 16:15                     ` Stan Shebs
2015-02-13 16:45                       ` Eli Zaretskii [this message]
2015-02-13 16:46                       ` Andreas Schwab
2015-02-13 18:05                     ` Pedro Alves
2015-02-15 11:53                       ` Corinna Vinschen
2015-01-19 16:05                 ` Eli Zaretskii
2015-01-31 23:31 ` Doug Evans

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=837fvl4v64.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=stanshebs@earthlink.net \
    /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).