From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5186] New: initramfs/cpio should support lzo compression
Date: Mon, 7 May 2012 15:54:04 +0200 [thread overview]
Message-ID: <20120507155404.6abbe051@skate> (raw)
In-Reply-To: <4FA672AD.2030905@mind.be>
Le Sun, 06 May 2012 14:46:37 +0200,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> PS What's the policy for reacting to patches posted on bugzilla?
AFAIK, there's none. Now that we have patchwork in place, I guess we
should probably tell users to not post patches to the Bugzilla, but to
the list instead (though that requires users to subscribe to the list).
What do you think?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-05-07 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 15:13 [Buildroot] [Bug 5186] New: initramfs/cpio should support lzo compression bugzilla at busybox.net
2012-05-06 12:46 ` Arnout Vandecappelle
2012-05-07 13:54 ` Thomas Petazzoni [this message]
2012-05-11 20:43 ` Arnout Vandecappelle
2012-05-14 19:09 ` Peter Korsgaard
2013-05-04 14:21 ` [Buildroot] [Bug 5186] " 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=20120507155404.6abbe051@skate \
--to=thomas.petazzoni@free-electrons.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