From: Marcus Osdoba <marcus.osdoba@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] util-linux: bump version to util-linux-ng 2.18
Date: Sun, 05 Dec 2010 21:17:55 +0100 [thread overview]
Message-ID: <4CFBF373.5060905@googlemail.com> (raw)
In-Reply-To: <c26a121c90a5cc9c26c391be4e9568913df61769.1291561083.git.smiley73@users.sourceforge.net>
Am 05.12.2010 16:00, schrieb heiko at zuerker.org:
> From: Heiko Zuerker<smiley73@users.sourceforge.net>
>
>
> Signed-off-by: Heiko Zuerker<smiley73@users.sourceforge.net>
> ---
> ...linux-2.13-pre17-hardcode-a-out-constants.patch | 41 --
> package/util-linux/util-linux-no-nls-fix.patch | 25 --
> package/util-linux/util-linux-susv3-legacy.patch | 429 --------------------
> package/util-linux/util-linux-umount2-fix.patch | 20 -
> package/util-linux/util-linux.mk | 9 +-
> 5 files changed, 5 insertions(+), 519 deletions(-)
> delete mode 100644 package/util-linux/util-linux-2.13-pre17-hardcode-a-out-constants.patch
> delete mode 100644 package/util-linux/util-linux-no-nls-fix.patch
> delete mode 100644 package/util-linux/util-linux-susv3-legacy.patch
> delete mode 100644 package/util-linux/util-linux-umount2-fix.patch
>
Hi,
I did similar work for version 2.17.2 some time ago. You can find my
work in bugzilla:
https://bugs.uclibc.org/show_bug.cgi?id=2677
Your version does not seem to use the autotargets infrastructure. Mine
does. Maybe you can use my version from bugzilla, update it to 2.18 and
present the developers a new patch.
Just a hint to prevent double work.
Regards,
Ossy
next prev parent reply other threads:[~2010-12-05 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 15:00 [Buildroot] [PATCH] util-linux: bump version to util-linux-ng 2.18 heiko at zuerker.org
2010-12-05 20:17 ` Marcus Osdoba [this message]
2010-12-05 20:24 ` Thomas Petazzoni
2010-12-05 20:42 ` Heiko Zuerker
2010-12-05 20:54 ` Marcus Osdoba
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=4CFBF373.5060905@googlemail.com \
--to=marcus.osdoba@googlemail.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.