From: Steven J. Hill <sjhill@realitydiluted.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/xfsprogs
Date: Fri, 21 Mar 2008 23:56:03 -0500 [thread overview]
Message-ID: <47E49163.5070805@realitydiluted.com> (raw)
In-Reply-To: <20080321180147.DA5513C342@busybox.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
ninevoltz at uclibc.org wrote:
> Author: ninevoltz
> Date: 2008-03-21 11:01:46 -0700 (Fri, 21 Mar 2008)
> New Revision: 21443
>
> Log:
> Fixed xfsprogs to build without needing bzero & bcopy. Patch by Nigel Kukard
>
Would you or Nigel please push this up to the xfsprogs maintainer(s)? These
legacy functions need to die and the only way they're going to is if we keep
pushing these back to the various package maintainers. Thanks.
- -Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH5JFjgyK5H2Ic36cRAq+QAJ9+9u4MjKi8VHJQ2e9YmDpPr9YIYwCeMgRw
Hn2+2Gmu+2o5jMQ1cCo83fo=
=C5Zy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-03-22 4:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 18:01 [Buildroot] svn commit: trunk/buildroot/package/xfsprogs ninevoltz at uclibc.org
2008-03-22 4:56 ` Steven J. Hill [this message]
2008-03-22 5:46 ` Nigel Kukard
-- strict thread matches above, loose matches on Subject: below --
2009-01-28 13:16 nkukard at uclibc.org
2009-01-28 13:14 nkukard at uclibc.org
2009-01-26 0:12 ulf at uclibc.org
2009-01-26 5:11 ` Nigel Kukard
2009-01-26 5:56 ` Peter Korsgaard
2009-01-11 21:50 ulf at uclibc.org
2008-12-31 18:25 nkukard at uclibc.org
2008-03-24 19:42 nkukard at uclibc.org
2008-03-24 19:23 nkukard at uclibc.org
2006-11-22 22:18 aldot 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=47E49163.5070805@realitydiluted.com \
--to=sjhill@realitydiluted.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