From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 667] New: [PATCH] e2fsprogs
Date: Sat, 17 Oct 2009 21:27:18 +0000 (UTC) [thread overview]
Message-ID: <bug-667-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=667
Summary: [PATCH] e2fsprogs
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Outdated package
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: rvpaasen at t3i.nl
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=703)
--> (https://bugs.busybox.net/attachment.cgi?id=703)
e2fsprogs package
Hi,
I have updated the e2fsprogs package to the new makefile format. I added the
tools from the 1.41.9 release of e2fsprogs that could not yet be (de)selected
(freefrag, e2undo) to the menu in Config.in.
Patch is attached and to be aplied to the current git.
Richard.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2009-10-17 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 21:27 bugzilla at busybox.net [this message]
2009-10-29 20:38 ` [Buildroot] [Bug 667] [PATCH] e2fsprogs bugzilla at busybox.net
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=bug-667-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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