From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001225]: Bump genext2fs
Date: Fri, 16 Feb 2007 05:19:13 -0800 [thread overview]
Message-ID: <ff31989c3cf04fa4990adc70cfb7fb26@busybox.net> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1225
======================================================================
Reported By: alexer
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1225
Category: New Features
Reproducibility: N/A
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 02-16-2007 05:19 PST
Last Modified: 02-16-2007 05:19 PST
======================================================================
Summary: Bump genext2fs
Description:
Just a new version, no more CVS-patches
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
02-16-07 05:19 alexer New Issue
02-16-07 05:19 alexer Status new => assigned
02-16-07 05:19 alexer Assigned To => buildroot
02-16-07 05:19 alexer File Added: genext2fs-1.4-upgrade.patch
======================================================================
next reply other threads:[~2007-02-16 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 13:19 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-16 13:23 [Buildroot] [buildroot 0001225]: Bump genext2fs bugs at busybox.net
2007-03-03 7:49 bugs at busybox.net
2007-03-20 16:43 bugs 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=ff31989c3cf04fa4990adc70cfb7fb26@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