From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Cris strace-4.5.18 patch
Date: Wed, 25 Feb 2009 11:07:13 +0100 [thread overview]
Message-ID: <49A51851.7080904@atmel.com> (raw)
In-Reply-To: <49A516ED.9050603@cetrtapot.si>
Hinko Kocevar wrote:
> Hans-Christian Egtvedt wrote:
>> On Wed, 25 Feb 2009 10:00:01 +0100
>> Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com> wrote:
>>
>>> On Wed, 25 Feb 2009 09:51:14 +0100
>>> Hinko Kocevar <hinko.kocevar@cetrtapot.si> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have this patch laying around for some time. I'm using it
>>>> for our cris embedded target and haven't had any issues with it.
>>>>
>>>> Please apply.
>>>>
>>> It does not apply at CVS HEAD, so I would recommend that you checkout
>>> the source code from CVS and rebase against it.
>>>
>> Woha, look at me, I'm on the strace-devel list as well and though this
>> was mailed there. You should email the patch there, so that it will be
>> included in mainline.
>>
>
> I'll do that and re-base the patch against CVS tree.
>
Good, then it will hopefully be included in the next release :)
>> For Buildroot you should make a patch changing what needs to be done in
>> SVN and adding your patch properly.
>
> Right, I don't have SVN commit permissions, so I'll resend the patch here. Is that OK?
>
Others can commit your patch to SVN. Remember that the patch to
Buildroot list must be against the patches Buildroot uses and that
specific version, while strace-devel wants a patch against current HEAD.
--
Best regards,
Hans-Christian Egtvedt
next prev parent reply other threads:[~2009-02-25 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 8:51 [Buildroot] Cris strace-4.5.18 patch Hinko Kocevar
2009-02-25 9:00 ` Hans-Christian Egtvedt
2009-02-25 9:03 ` Hans-Christian Egtvedt
2009-02-25 10:01 ` Hinko Kocevar
2009-02-25 10:07 ` Hans-Christian Egtvedt [this message]
2009-02-25 10:11 ` Peter Korsgaard
2009-02-25 15:24 ` Hinko Kocevar
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=49A51851.7080904@atmel.com \
--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 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.