From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/binutils
Date: Mon, 9 Mar 2009 09:09:43 +0100 [thread overview]
Message-ID: <20090309090943.64c1d450@hcegtvedt> (raw)
In-Reply-To: <87r617ceh0.fsf@macbook.be.48ers.dk>
On Mon, 09 Mar 2009 09:00:59 +0100
Peter Korsgaard <jacmet@uclibc.org> wrote:
> >>>>> "Hans-Christian" == Hans-Christian Egtvedt
> >>>>> <hans-christian.egtvedt@atmel.com> writes:
>
> Hans-Christian> Last news, about a month ago, is that the legal
> Hans-Christian> papers are gathering signatures. First attempt to
> Hans-Christian> gather signatures lead to a deadlock, FSF waiting for
> Hans-Christian> Atmel, Atmel waiting for FSF. But now they are,
> Hans-Christian> AFAIK, back on track.
>
> Thanks - Ok, that's all the legal stuff - But what about the technical
> work? I guess the FSF isn't particular interested in patches against
> binutils 2.18 from 2007?
>
Atmel will submit patches against current HEAD/trunk of course.
--
Best regards,
Hans-Christian Egtvedt
next prev parent reply other threads:[~2009-03-09 8:09 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 22:09 [Buildroot] svn commit: trunk/buildroot/toolchain/binutils jacmet at uclibc.org
2009-03-06 17:56 ` Thiago A. Corrêa
2009-03-06 21:21 ` Peter Korsgaard
2009-03-08 2:20 ` Thiago A. Corrêa
2009-03-09 5:58 ` Hans-Christian Egtvedt
2009-03-09 8:00 ` Peter Korsgaard
2009-03-09 8:09 ` Hans-Christian Egtvedt [this message]
2009-03-09 8:24 ` Peter Korsgaard
2009-03-09 8:37 ` Hans-Christian Egtvedt
-- strict thread matches above, loose matches on Subject: below --
2009-03-05 13:40 jacmet at uclibc.org
2009-03-03 22:09 jacmet at uclibc.org
2009-02-10 15:48 jacmet at uclibc.org
2009-01-03 16:24 ulf at uclibc.org
2009-01-03 1:06 ulf at uclibc.org
2009-01-03 0:59 ulf at uclibc.org
2009-01-03 15:05 ` Nigel Kukard
2009-01-03 15:02 ` Ulf Samuelsson
2009-01-03 15:15 ` Ulf Samuelsson
2009-01-02 20:30 jacmet at uclibc.org
2008-12-18 16:52 jacmet at uclibc.org
2008-12-09 11:38 egtvedt at uclibc.org
2008-12-09 10:41 Hans-Christian Egtvedt
2008-12-09 10:09 egtvedt at uclibc.org
2008-12-09 10:23 ` Bernhard Reutner-Fischer
2008-12-09 10:30 ` Hans-Christian Egtvedt
2008-12-09 10:33 ` Bernhard Reutner-Fischer
2008-12-09 11:35 ` Hans-Christian Egtvedt
2008-12-05 15:27 jacmet at uclibc.org
2008-12-05 15:27 jacmet at uclibc.org
2008-03-11 15:49 ninevoltz at uclibc.org
2008-03-11 15:54 ` Nigel Kukard
[not found] ` <46a136670803110914l7cf179c6m5c866f53b4963bbf@mail.gmail.com>
2008-03-11 16:42 ` Nigel Kukard
2007-09-17 12:42 ulf at uclibc.org
2007-09-17 11:19 aldot at uclibc.org
2007-09-01 16:37 aldot at uclibc.org
2007-08-22 9:22 aldot at uclibc.org
2007-08-20 13:00 aldot at uclibc.org
2007-08-20 14:52 ` Ulf Samuelsson
2007-08-20 18:18 ` Cristian Ionescu-Idbohrn
2007-08-21 13:32 ` Bernhard Fischer
2007-08-21 13:48 ` Thiago A. Corrêa
2007-08-17 23:06 ulf at uclibc.org
2007-05-15 11:28 aldot at uclibc.org
2007-01-28 16:38 aldot at uclibc.org
2007-01-16 13:24 aldot at uclibc.org
2006-12-13 23:18 aldot at uclibc.org
2006-12-13 19:55 aldot at uclibc.org
2006-12-02 19:02 vapier at uclibc.org
2006-10-21 5:34 vapier at uclibc.org
2006-09-27 22:48 vapier at uclibc.org
2006-09-27 22:44 vapier at uclibc.org
2006-08-24 3:40 vapier at uclibc.org
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=20090309090943.64c1d450@hcegtvedt \
--to=hans-christian.egtvedt@atmel.com \
--cc=buildroot@busybox.net \
/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