Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Sean Chen <sean.chen1234@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: The abbreviation in []
Date: Wed, 06 Jan 2010 06:51:00 -0000	[thread overview]
Message-ID: <20100106065111.GE24777@adacore.com> (raw)
In-Reply-To: <5e81cb501001052233t5a7ce6a4hbbfe4637bd4e2494@mail.gmail.com>

> You are right that CONTRIBUTE and MAINTAINERS have already included
> much information. However, they don't include some trivial questions
> like abbreviation or posting style (top-posting / bottom-posting). :)
> Anyway, this is not a block issue and we can guess and learn it by
> reading the threads.

Perhaps, if you have some time, you could help us improve the situation?
Some of us have been hacking on GDB for long enough that we don't
realize that these sorts of questions are not obvious, so your
feedback is important.

I had a look at the GDB website, and the "contribute" page
(http://www.sourceware.org/gdb/contribute/, click on "contributing"
at the top of the main web page) has a short text pointing to
the CONTRIBUTE file. If you are willing to send patches to this file,
I'm sure Eli and/or I are willing to review them (Eli is our documentation
maintainer).

-- 
Joel


  reply	other threads:[~2010-01-06  6:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05  1:06 Sean Chen
2010-01-05  5:00 ` Joel Brobecker
2010-01-05 15:46   ` Sean Chen
2010-01-05 17:42     ` Joel Brobecker
2010-01-06  6:33       ` Sean Chen
2010-01-06  6:51         ` Joel Brobecker [this message]
2010-01-06  7:56           ` Sean Chen
2010-01-06  8:03             ` Joel Brobecker
2010-01-06  8:16               ` Sean Chen
2010-01-06  8:35                 ` Joel Brobecker
2010-01-06  9:01                   ` Sean Chen
2010-01-06  9:26                     ` Hui Zhu

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=20100106065111.GE24777@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sean.chen1234@gmail.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