Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: danny.backx@scarlet.be
Cc: gdb-patches@sourceware.org
Subject: Re: Patch : gdbserver get_image_name on CE
Date: Sun, 07 Jun 2009 19:28:00 -0000	[thread overview]
Message-ID: <200906072029.14094.pedro@codesourcery.com> (raw)
In-Reply-To: <1244401967.11918.226.camel@pavilion>

On Sunday 07 June 2009 20:12:47, Danny Backx wrote:
> On Sun, 2009-06-07 at 19:16 +0100, Pedro Alves wrote:
> > It's fine to send unfinished patches for comments, if you'd like, but
> > please say so explicitly, so I don't waste time trying to understand
> > what they're for, for nothing.
> 
> This one isn't for nothing, it fixes a problem. 

Sorry, you missed my point.  "for nothing" refered to my waste of time,
not to the usefulness of the patch.  Please do realize that if you don't
explain what the patch does, than whoever reviews it has to stare
at the code and try to make some sense of it.  If the patch
isn't obvious (this one isn't obvious to me), and doesn't
come with explanations, it is not going to be applied.  The onus
is on you to make it as easy as possible for a reviewer/maintainer to
accept a patch.  I really do not mean to sound harsh.  It is just
that it is easy to not realise that it does take time to review
a patch, and the backlog isn't getting shorter...

> It's just not all of the 
> work to get gdb/gdbserver to work for x86/ce .

I understand.

On Sunday 07 June 2009 20:12:47, Danny Backx wrote:
> CE -> unicode, both ARM and x86.
> The DLL name was in the right place, it's just the code to read it
> didn't work right.

It's the explanation of what's wrong with it that's missing.

-- 
Pedro Alves


  reply	other threads:[~2009-06-07 19:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-07  9:18 Danny Backx
2009-06-07 17:03 ` Pedro Alves
2009-06-07 18:02   ` Danny Backx
2009-06-07 18:15     ` Pedro Alves
2009-06-07 19:13       ` Danny Backx
2009-06-07 19:28         ` Pedro Alves [this message]
2009-06-08 18:13           ` Danny Backx
2009-06-12 22:18       ` Danny Backx
2009-06-13  6:28         ` Johnny Willemsen
2009-06-13 14:29 Danny Backx
2009-06-13 18:05 ` Pedro Alves
2009-06-13 18:08   ` Pedro Alves
2009-06-14  8:35     ` Danny Backx
2009-06-14 13:56       ` Pedro Alves
2009-06-14  8:47   ` Danny Backx
2009-06-14  9:48     ` Danny Backx
2009-06-14 14:23       ` Pedro Alves
2009-06-21  9:50         ` Danny Backx
2009-06-30 21:07           ` Danny Backx
2009-06-30 21:56             ` Pedro Alves
2009-07-01 18:41               ` Danny Backx
2009-07-01 18:52                 ` Pedro Alves
2009-07-01 19:12                   ` Danny Backx
2009-07-01 20:12                 ` Pedro Alves
2009-07-04 18:14                   ` Pedro Alves
2009-07-08  9:55                     ` Danny Backx
2009-07-08 11:34                       ` Danny Backx
2009-07-27 20:40                         ` Danny Backx
2009-07-01 19:31               ` Danny Backx
2009-06-14 14:34       ` Pedro Alves
2009-06-14 14:05     ` Pedro Alves

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=200906072029.14094.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=danny.backx@scarlet.be \
    --cc=gdb-patches@sourceware.org \
    /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