From: Arkadiusz Miskiewicz <arekm@maven.pl>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Karel Zak <kzak@redhat.com>,
linux-kernel@vger.kernel.org, Henne Vogelsang <hvogel@suse.de>,
Olaf Hering <olh@suse.de>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: util-linux: orphan
Date: Mon, 18 Dec 2006 11:05:13 +0100 [thread overview]
Message-ID: <200612181105.13893.arekm@maven.pl> (raw)
In-Reply-To: <Pine.LNX.4.61.0612181031210.21739@yvahk01.tjqt.qr>
On Monday 18 December 2006 10:33, Jan Engelhardt wrote:
> > after few weeks I'm pleased to announce a new "util-linux-ng" project.
> > This project is a fork of the original util-linux (2.13-pre7).
> >
> > The goal of the project is to move util-linux code back to useful state,
> > sync with actual distributions and kernel and make development more
> > transparent end open.
>
> If Adrian [ http://lkml.org/lkml/2006/11/9/262 ] does not want to be
> the maintainer, ask if you can take over, including the name.
> This smells a lot like the RPM case [ http://lwn.net/Articles/196523/ ]
> however, it does not look like anyone is going to call it rpm-ng just
> because the original name is owned by the last maintainer.
rpm.org case is even worse. Original maintainer still develops rpm - at this
moment version 4.4.7 at http://wraptastic.org/ (while rpm.org starts from
older 4.4.2 codebase), there is active mailing list, so we have two running
projects with the same name which is bad thing and will cause confusion.
I hope that there will be one util-linux and one rpm project.
> Regards,
> -`J'
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
next prev parent reply other threads:[~2006-12-18 10:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 7:52 [ANNOUNCE] util-linux-ng Karel Zak
2006-12-18 8:35 ` Ian Kent
2006-12-18 8:50 ` Karel Zak
2006-12-18 9:55 ` Arkadiusz Miskiewicz
2006-11-09 22:41 ` util-linux: orphan Karel Zak
2006-11-09 22:45 ` H. Peter Anvin
2006-11-10 10:02 ` Pádraig Brady
2006-12-18 7:17 ` Karel Zak
2006-12-18 9:33 ` Jan Engelhardt
2006-12-18 10:05 ` Arkadiusz Miskiewicz [this message]
2006-12-18 10:49 ` Matthias Koenig
2006-12-18 15:00 ` Karel Zak
2006-12-27 2:46 ` Arnd Bergmann
2006-12-27 3:08 ` H. Peter Anvin
2006-12-27 3:58 ` Arnd Bergmann
2006-12-27 4:35 ` Theodore Tso
2006-12-27 11:24 ` Alessandro Suardi
2006-12-27 11:46 ` Jan Engelhardt
2006-12-27 13:18 ` Horst H. von Brand
2006-12-27 13:24 ` Christoph Hellwig
2006-12-27 4:17 ` Chris Adams
2006-12-27 18:15 ` Karel Zak
2006-12-27 18:39 ` Arnd Bergmann
2006-12-27 19:18 ` Karel Zak
2006-12-27 20:42 ` Theodore Tso
2006-12-27 22:12 ` Karel Zak
2006-12-27 22:21 ` H. Peter Anvin
2006-12-30 7:31 ` Valdis.Kletnieks
2006-12-28 10:28 ` Ian Kent
2006-12-18 10:40 ` [ANNOUNCE] util-linux-ng Ian Kent
2006-12-20 12:19 ` Jens Axboe
2006-12-20 14:55 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2006-12-20 6:42 util-linux: orphan Albert Cahalan
2006-12-20 16:13 ` Jan Engelhardt
2006-12-20 17:27 ` Albert Cahalan
2006-12-21 20:09 ` Jan Engelhardt
[not found] <fa.LNsUrtZq/ifve7DpPe6aiVU8Usk@ifi.uio.no>
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=200612181105.13893.arekm@maven.pl \
--to=arekm@maven.pl \
--cc=hpa@zytor.com \
--cc=hvogel@suse.de \
--cc=jengelh@linux01.gwdg.de \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
/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
Powered by JetHome