mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Kent <ikent@redhat.com>
To: Karel Zak <kzak@redhat.com>
Cc: linux-kernel@vger.kernel.org, util-linux-ng@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng
Date: Mon, 18 Dec 2006 17:35:29 +0900	[thread overview]
Message-ID: <1166430929.3610.3.camel@raven.themaw.net> (raw)
In-Reply-To: <20061218075210.GB5217@petra.dvoda.cz>

On Mon, 2006-12-18 at 08:52 +0100, Karel Zak wrote:
> 
>  I'm pleased to announce a new "util-linux-ng" project. This project
>  is a fork of the original util-linux (2.13-pre7). 

Perhaps forwarding this to fs-devel would be good also.

> 
>  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.
> 
>  The short term goals (for 2.13 release):
> 
> 	- remove all NFS code from util-linux-ng 
>           (/sbin/mount.nfs from nfs-utils is replacement)
> 	- remove FS/device detection code
>           (libblkid from e2fsprogs or libvolumeid is replacement)
> 	- move as much as possible patches from distributions to upstream
> 
>  Mailing list:
>    http://vger.kernel.org/vger-lists.html#util-linux-ng
> 
>  FTP:
>    ftp://ftp.kernel.org/pub/scm/utils/util-linux-ng/
> 
>  GIT:
>    git clone git://git.kernel.org/pub/scm/utils/util-linux-ng/util-linux-ng.git util-linux-ng
> 
>    [Note, GIT repo contains previous 47 versions of util-linux.]
> 
>         
>  The mailing list or my private e-mail are open for your patches, ideas and
>  suggestion. The mailing list is also place where you can help us review
>  patches.
> 
>     Karel
> 


  reply	other threads:[~2006-12-18  8:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18  7:52 Karel Zak
2006-12-18  8:35 ` Ian Kent [this message]
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
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
     [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=1166430929.3610.3.camel@raven.themaw.net \
    --to=ikent@redhat.com \
    --cc=kzak@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=util-linux-ng@vger.kernel.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

Powered by JetHome