From: Daniel Baumann <daniel-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
Cc: sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: proper name for userspace package?
Date: Mon, 03 Aug 2009 22:04:38 +0200 [thread overview]
Message-ID: <4A7742D6.9050405@debian.org> (raw)
In-Reply-To: <20090804.041006.12536354.ryusuke-sG5X7nlA6pw@public.gmane.org>
Ryusuke Konishi wrote:
> "nilfs-tools" sounds simpler. Umm, actually it would be better in the
> long term because the nilfs package already has versions related to
> the filesystem version (e.g. -2.x.y). At least I don't have any
> reason to object to the rename.
ok, i think so too. i just renamed in debian (well, i've uploaded it..
it will not wait for 0 to \infty for ftp-masters re-approval in the NEW
queue :/).
> I just realized that ocfs2-tools package has versions 1.x.y.
i heard, that ocfs2 is called ocfs2 because ocfs1 was oracle intern
only. not sure if that's true though.
--
Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email: daniel.baumann-uDfGT2BMUjhJc61us3aD9uTW4wlIGRCZ@public.gmane.org
Internet: http://people.panthera-systems.net/~daniel-baumann/
next prev parent reply other threads:[~2009-08-03 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 16:29 proper name for userspace package? Eric Sandeen
[not found] ` <4A71CA72.8080106-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-07-30 17:32 ` Ryusuke Konishi
[not found] ` <20090731.023234.56054455.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-07-30 17:50 ` Eric Sandeen
2009-07-30 18:36 ` Daniel Baumann
[not found] ` <4A71E82C.1040208-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2009-08-03 19:10 ` Ryusuke Konishi
[not found] ` <20090804.041006.12536354.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-03 20:04 ` Daniel Baumann [this message]
[not found] ` <4A7742D6.9050405-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2009-08-05 11:32 ` Chris Samuel
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=4A7742D6.9050405@debian.org \
--to=daniel-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=ryusuke-sG5X7nlA6pw@public.gmane.org \
--cc=sandeen-H+wXaHxf7aLQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.