public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Danny Backx <danny.backx@scarlet.be>
Cc: binutils <binutils@sourceware.org>
Subject: Re: Binutils on arm : pls advice me how to proceed
Date: Thu, 04 May 2006 18:03:00 -0000	[thread overview]
Message-ID: <20060504180348.GA5785@nevyn.them.org> (raw)
In-Reply-To: <1146765307.4177.16.camel@dannypc>

On Thu, May 04, 2006 at 07:55:07PM +0200, Danny Backx wrote:
> Pedro Alves and I sent some message on the list that indicate where we
> think some of the problem areas are.
> 
> Clearly, something must be wrong with those messages, as there appears
> to be little attention being payed to them.
> 
> Can someone help me by telling me what I'm missing ?
> Am I sending the wrong information ?
> Am I talking to the wrong public ?
> Am I boring and should I just shut up ? :-)

The maintainers are always busy; it sometimes takes a long time and a
couple of tries to get a response.  Patience is very important.
Fixes for WinCE don't normally get a lot of attention, because there's
a relatively small user base.

FWIW, I skimmed some of the patches that have been sent; #ifdefs
are rarely OK.  Although some are probably needed since the WinCE
loader is so different from typical ARM loaders, it's important to
minimize them, and to figure out (A) what the differences are supposed
to be, and (B) where the most effective place to implement the changes
is.  Another thing that helps to make your changes clear is new
testcases; if there had been enough testcases for the special WinCE
needs, it probably wouldn't have broken.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2006-05-04 18:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 17:55 Danny Backx
2006-05-04 18:03 ` Daniel Jacobowitz [this message]
2006-05-04 19:03   ` Pedro Alves
2006-05-05 17:46     ` Nick Clifton
2006-05-10 15:14     ` Nick Clifton
2006-05-11  4:32       ` Danny Backx
2006-05-11  6:37         ` Pedro Alves
2006-05-11 14:59         ` Nick Clifton
2006-05-11  8:51       ` Pedro Alves
2006-05-11 14:54         ` Nick Clifton

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=20060504180348.GA5785@nevyn.them.org \
    --to=drow@false.org \
    --cc=binutils@sourceware.org \
    --cc=danny.backx@scarlet.be \
    /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).