public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Greg KH <greg@kroah.com>
Cc: clemens@dwf.com, linux-hotplug-devel@lists.sourceforge.net,
	KML <linux-kernel@vger.kernel.org>,
	reg@orion.dwf.com
Subject: Re: [ANNOUNCE] udev 003 release
Date: Tue, 21 Oct 2003 03:11:19 +0200	[thread overview]
Message-ID: <1066698679.10221.178.camel@nosferatu.lan> (raw)
In-Reply-To: <20031021005025.GA28269@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 2084 bytes --]

On Tue, 2003-10-21 at 02:50, Greg KH wrote:

> > Three questions if you do not mind:
> > 
> > 1)  Is it possible to maintain naming of tarball/version ?  Meaning,
> >     say we forget about the 003 version, could the next be 0.4, or even
> >     0.3.1 or whatever ?  Just changing makes trying to keep packages
> >     sane a hassle.  Thanks :)
> 
> The naming will be consistant from now on.  Next release will be 004,
> followed by 005, and so on.  Remember, version numbers mean nothing :)
> 

Well, if you had an 0.2 already, 003 sorda comes and screw the pooch 
(if trying to work with a package manager - although it seems we are
OK with ours seeing 003 as the later) :)

> >     If not, any idea if/when udev will start following official
> >     libsysfs?  Yes, not a biggie, but it would be nice to have
> >     sysfsutils its own package :)
> 
> I just got a patch today from Dan that merged the latest version of
> libsysfs into udev.  It's in the udev bk tree already.  libsysfs will
> always be a copy in the udev tree, as udev links statically, and it
> keeps the build process and debug process much easier.
> 
> sysfsutils can still be its own package, other programs are starting to
> use libsysfs already.
> 

Ok, ill have a look at the bk tree at som stage, thanks.

> > 3)  Any plans to have namedev support wildcarts ?  Like:
> > 
> >   dsp*:root:audio:0660
> >   audio*:root:audio:0660
> >   midi*:root:audio:0660
> >   mixer*:root:audio:0660
> 
> Yes, I would love to support that.  Care to send a patch?  :)
> 

:P  I wont promise, as my schedule is a bit tight, but I'll send
along if I get to cook something up.

> Of course you need a kernel patch for the sound class that is only
> available in my kernel tree right now for sound devices to work with
> udev...
> 

Need help testing ? :) (Yes, I am a lazy bastard, and a patch against
test8 would help if you needed the testing)


Thanks,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-10-21  1:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17  5:56 [ANNOUNCE] udev 003 release Greg KH
2003-10-17  6:32 ` Clemens Schwaighofer
2003-10-17 17:57 ` clemens
2003-10-17 18:19   ` Greg KH
2003-10-17 18:27     ` Greg KH
2003-10-21  0:39       ` Martin Schlemmer
2003-10-21  0:50         ` Greg KH
2003-10-21  1:11           ` Martin Schlemmer [this message]
2003-10-21  2:43             ` Greg KH
2003-10-21  3:38               ` Martin Schlemmer
2003-10-21 17:44                 ` Greg KH
2003-10-21 20:20                   ` Martin Schlemmer
2003-10-21 20:56                     ` Greg KH

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=1066698679.10221.178.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=clemens@dwf.com \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reg@orion.dwf.com \
    /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