From: "Baars, M.J." <mjbaars1977.gdb@gmail.com>
To: Tom Tromey <tromey@redhat.com>, gdb@sourceware.org
Subject: Re: print_npx_status_word
Date: Fri, 15 Apr 2011 16:28:00 -0000 [thread overview]
Message-ID: <4DA87235.7060003@gmail.com> (raw)
In-Reply-To: <m3ei53efd8.fsf@fleche.redhat.com>
On 04/15/2011 04:52 PM, Tom Tromey wrote:
> Michael> I don't see the point, maybe you can help me a little... could you
> Michael> please explain in a little more detail why my patch isn't accepted and
> Michael> why my email doesn't appear on the list, while you can still answer to
> Michael> it?
>
> Your email showed up on the list for me.
Oh, ok. So at least the email itself should function.
Can you see this appear on the mailing list???
> CONTRIBUTE says a number of things you must do to submit a patch.
> One is that you should submit uni- or context-diffs.
> Also you need to explain what the patch does.
> Also you need to follow the GNU coding standards.
I'll have a look at it again, but if I remember correctly I don't
exactly concur with the coding standards as they are. I'll see what I
can do though.
> Tom
Michael
next prev parent reply other threads:[~2011-04-15 16:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 15:44 print_npx_status_word Baars, M.J.
2011-04-14 16:06 ` print_npx_status_word Tom Tromey
[not found] ` <4DA7ED79.3000400@gmail.com>
[not found] ` <m3ei53efd8.fsf@fleche.redhat.com>
2011-04-15 16:28 ` Baars, M.J. [this message]
2011-04-15 16:32 ` print_npx_status_word Tom Tromey
[not found] ` <4DA87479.50203@gmail.com>
[not found] ` <m3lizbcvt7.fsf@fleche.redhat.com>
2011-04-16 6:09 ` print_npx_status_word Baars, M.J.
2011-04-16 8:24 ` print_npx_status_word Mark Kettenis
2011-04-16 13:46 ` print_npx_status_word Baars, M.J.
2011-04-16 14:29 ` print_npx_status_word Daniel Jacobowitz
2011-04-16 16:21 ` print_npx_status_word Baars, M.J.
2011-04-16 16:33 ` print_npx_status_word Mark Kettenis
2011-04-16 16:47 ` print_npx_status_word Baars, M.J.
2011-04-16 17:10 ` print_npx_status_word Mark Kettenis
2011-04-16 17:55 ` print_npx_status_word Baars, M.J.
2011-04-16 18:07 ` print_npx_status_word Marek Polacek
2011-04-18 17:00 ` print_npx_status_word Tom Tromey
2011-04-16 16:45 ` print_npx_status_word Eli Zaretskii
[not found] ` <4DA99DA1.2090708__5871.13250880993$1302961604$gmane$org@gmail.com>
2011-04-18 17:04 ` print_npx_status_word Tom Tromey
2011-04-19 19:01 ` print_npx_status_word Baars, M.J.
2011-04-19 19:53 ` print_npx_status_word Pedro Alves
2011-04-18 17:04 ` print_npx_status_word Tom Tromey
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=4DA87235.7060003@gmail.com \
--to=mjbaars1977.gdb@gmail.com \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.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