From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: Daniel Baumann <daniel-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: FYI: nilfs2 in Debian
Date: Thu, 01 May 2008 17:54:02 +0900 [thread overview]
Message-ID: <1209632042.3250.52.camel@localhost.localdomain> (raw)
In-Reply-To: <48132AE8.7060305-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Hi Daniel,
On Sat, 2008-04-26 at 15:15 +0200, Daniel Baumann wrote:
> Hi,
>
> I've uploaded nilfs2 and nilfs2-tools to Debian. They are present in
> unstable, and soon migrate to testing, which means that nilfs2 will be
> present in the upcoming new stable release of Debian, called 5.0 "lenny".
>
> Later, I'll add it to linux-modules-extra-2.6, so that pre-build module
> packages for all Debian default kernel images are available (see [0] for
> more information about kernel modules packaging in Debian).
>
> Regards,
> Daniel
>
> [0]
> http://blog.daniel-baumann.ch/2006/12/10#20061210_kernel-modules-packaging
Thank you for uploading nilfs2 and nilfs2-tools to Debian sid,
and thank you for letting us know about their nearest packaging plan.
We will revise our web page for Debian package, and would also like
to stop serving non-official packages for lenny to avoid overlap
when your packages will migrate to lenny.
If you have any problem in pursuing the plan, please let us know.
Best regards,
--
Ryusuke Konishi
NILFS team NTT
http://www.nilfs.org/
prev parent reply other threads:[~2008-05-01 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 13:15 FYI: nilfs2 in Debian Daniel Baumann
[not found] ` <48132AE8.7060305-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2008-05-01 8:54 ` Ryusuke Konishi [this message]
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=1209632042.3250.52.camel@localhost.localdomain \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=daniel-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org \
/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