From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/gdb
Date: Fri, 08 Feb 2008 12:45:21 +0200 [thread overview]
Message-ID: <47AC32C1.8070706@promwad.com> (raw)
In-Reply-To: <200802081007.30537.atle@nissestad.no>
Thanks for hint, I indeed forgot to svn add.
Regards,
Ivan
Atle Nissestad wrote:
> On Thursday 7. February 2008 11:59:01 vanokuten at uclibc.org wrote:
>> Author: vanokuten
>> Date: 2008-02-07 02:59:00 -0800 (Thu, 07 Feb 2008)
>> New Revision: 20953
>>
>> Log:
>> updated gdb support for nios2, thanks Atle
>>
>> Modified:
>> trunk/buildroot/toolchain/gdb/Config.in
>>
>>
>> Changeset:
>> Modified: trunk/buildroot/toolchain/gdb/Config.in
>
> Seems you missed the important part of my patch, the actual nios2 gdb 6.6
> arch-support (/buildroot/toolchain/gdb/6.6/700-nios2-6.6.patch).
> Forgot to 'svn add' perhaps ..?
>
> - Atle
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2008-02-08 10:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 10:59 [Buildroot] svn commit: trunk/buildroot/toolchain/gdb vanokuten at uclibc.org
2008-02-08 9:07 ` Atle Nissestad
2008-02-08 10:45 ` Ivan Kuten [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-08 8:54 jacmet at uclibc.org
2008-12-08 8:46 jacmet at uclibc.org
2008-12-08 8:46 jacmet at uclibc.org
2008-12-07 21:22 jacmet at uclibc.org
2008-08-24 7:48 jacmet at uclibc.org
2008-07-01 21:46 ulf at uclibc.org
2008-07-01 21:38 ulf at uclibc.org
2008-07-01 21:36 ulf at uclibc.org
2008-06-16 15:52 jacmet at uclibc.org
2007-09-26 14:16 aldot at uclibc.org
2007-07-29 17:34 ulf at uclibc.org
2007-06-26 14:32 aldot at uclibc.org
2007-06-22 10:42 aldot at uclibc.org
2007-06-16 17:55 sjhill 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=47AC32C1.8070706@promwad.com \
--to=ivan.kuten@promwad.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.