From: "Björn Haase" <bjoern.m.haase@web.de>
To: binutils@sourceware.org
Subject: Re: maintainer update: add support for more AVR microcontrollers
Date: Sat, 22 Apr 2006 14:20:00 -0000 [thread overview]
Message-ID: <200604210959.19519.bjoern.m.haase@web.de> (raw)
From: Joerg Wunsch <j@uriah.heep.sax.de>, To: Eric Christopher
<echristo@apple.com>,
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>, binutils@sourceware.org, Date: Thu,
20 Apr 2006 23:01:23 +0200, Subject:
References:
<20060419193241.GA77330@uriah.heep.sax.de> <20060420014708.GM13324@lug-owl.de>
<234616A5-B9B9-4A30-867D-3CD053064067@apple.com>
<20060420050834.GC73791@uriah.heep.sax.de>
<F610553E-74F0-44C0-AA67-94EC0BD0DD70@apple.com>, Reply-to: Joerg Wunsch
<joerg_wunsch@uriah.heep.sax.de>
I completely agree with Joerg. IMO there is *NO* present user of the gnu
toolchain for AVR that is not aware of the fact that the best place to find
recent documentation is the avr-libc project. I'd like to estimate that 95%
of the users even would not know how to access the information on the
binutils info pages :-).
Without Joerg's changes the binutils port was extremely outdated. The only
reason why this did not cause difficulties is, that almost every user has
been working with pre-compiled binaries that were generated with the patches
that were distributed and maintained by the maintainers of the avr-libc
projects (thank's to Joerg Wunsch and Eric Weddington IIRC :-) ).
So the private binutils version of Joerg generally has a more official status
than the cvs version :-).
Yours,
Bjoern.
next reply other threads:[~2006-04-21 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-22 14:20 Björn Haase [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-20 1:52 Joerg Wunsch
2006-04-20 10:51 ` Jan-Benedict Glaw
2006-04-20 10:53 ` Eric Christopher
2006-04-20 11:05 ` Joerg Wunsch
2006-04-20 14:24 ` Eric Christopher
2006-04-21 6:55 ` Joerg Wunsch
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=200604210959.19519.bjoern.m.haase@web.de \
--to=bjoern.m.haase@web.de \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).