From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000502]: device-mapper: new version
Date: Mon, 12 Feb 2007 05:47:39 -0800 [thread overview]
Message-ID: <bc2fc0788d9f6b855b4f50b007d0a0c8@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=502
======================================================================
Reported By: deac
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 502
Category: New Features
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 10-24-2005 09:21 PDT
Last Modified: 02-12-2007 05:47 PST
======================================================================
Summary: device-mapper: new version
Description:
device-manager has a new version: 1.01.05
it must be installed to compile lvm2-1.01*.
(see also next bug of me)
the dm.mk must be patched.
in this patch, theres also a "rm -f $@" instead "rm $@"
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
10-24-05 09:21 deac New Issue
10-24-05 09:21 deac Status new => assigned
10-24-05 09:21 deac Assigned To => uClibc
10-24-05 09:21 deac File Added: dm.mk.patch
01-24-06 13:09 prpplague Status assigned => resolved
01-24-06 13:09 prpplague Resolution open => fixed
01-24-06 13:09 prpplague Additional Information Updated
03-08-06 16:53 vapier Status resolved => closed
02-12-07 05:47 vapier Status closed => assigned
02-12-07 05:47 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bc2fc0788d9f6b855b4f50b007d0a0c8@bugs.busybox.net \
--to=bugs@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