From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] target-finalize: fix libthread_db strip fix
Date: Mon, 29 Nov 2010 15:44:26 -0500 [thread overview]
Message-ID: <201011291544.27824.vapier@gentoo.org> (raw)
In-Reply-To: <87vd3gxsp7.fsf@macbook.be.48ers.dk>
On Monday, November 29, 2010 06:41:40 Peter Korsgaard wrote:
> >>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
> Mike> which would be nice to know ... from my point of view, these are
> Mike> simply being ignored with no feedback. but perhaps this gets
> Mike> back to the buildroot doc not really covering any dev/release
> Mike> processes yet.
>
> True. We follow the same general structure as a bunch of other projects
> (E.G. Linux, u-boot, barebox, ..).
by "structure", i'm guessing you mean "release/development process" ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101129/b34e914c/attachment.pgp>
next prev parent reply other threads:[~2010-11-29 20:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 22:43 [Buildroot] [PATCH] target-finalize: fix libthread_db strip fix Mike Frysinger
2010-11-28 10:09 ` Peter Korsgaard
2010-11-28 17:36 ` Mike Frysinger
2010-11-28 21:14 ` Peter Korsgaard
2010-11-28 22:13 ` Mike Frysinger
2010-11-29 7:53 ` Peter Korsgaard
2010-11-29 11:21 ` Mike Frysinger
2010-11-29 11:41 ` Peter Korsgaard
2010-11-29 20:44 ` Mike Frysinger [this message]
2010-11-29 21:14 ` Peter Korsgaard
2010-11-29 23:45 ` Mike Frysinger
2010-11-28 22:25 ` Mike Frysinger
2010-11-29 7:57 ` Peter Korsgaard
2010-11-29 11:18 ` Mike Frysinger
2010-11-29 11:38 ` Peter Korsgaard
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=201011291544.27824.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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.