From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Next problem, rpm organization
Date: Tue, 12 Jun 2001 14:35:55 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-99235670124629@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99210624825359@msgid-missing>
I think I see what's going on ... the last released version doesn't
match CVS, and I never got any responses from you for the last
sets of patches I sent. Some of them got in, attributed to other
folk (like GregKH for my man page updates).
Net result is that the "usbmodules" in your release doesn't work
with "shipping" 2.4 kernels/modutils. So it doesn't help much for
anyone wanting hotplug support ...
The most up-to-date release I know about is linked from:
http://linux-hotplug.sourceforge.net/?selected=setup
That's got RPMs (more current spec file, installs in a better
place...) and various patches that you haven't released. I don't
know if that includes _all_ those patches though. It shouldn't
be too different from your CVS if you did incorporate all the
patches that were sent to you.
Minor problem with usbmodules, worth fixing: it doesn't
handle "# ..." style comment syntax.
- Dave
----- Original Message -----
From: "Thomas Sailer" <sailer@scs.ch>
To: "David Brownell" <david-b@pacbell.net>
Cc: "Stephen Williams" <steve@icarus.com>; <linux-hotplug-devel@lists.sourceforge.net>
Sent: Tuesday, June 12, 2001 4:14 AM
Subject: Re: Next problem, rpm organization
> David Brownell schrieb:
>
> > Particularly since Thomas' utilities haven't incorporated patches for
> > some time, and the most current stuff is linked to from the hotplug
> > website ... there's even a spec file all set up!
>
> That's not true, I have incorporated all patches I'm aware of
> into usb.in.tum.de CVS.
>
> Tom
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-06-12 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-09 17:03 Next problem, rpm organization Stephen Williams
2001-06-11 16:11 ` Greg KH
2001-06-11 16:32 ` Stephen Williams
2001-06-11 16:37 ` Greg KH
2001-06-11 17:05 ` David Brownell
2001-06-11 17:52 ` David Brownell
2001-06-11 17:52 ` Stephen Williams
2001-06-11 18:04 ` David Brownell
2001-06-11 18:22 ` Stephen Williams
2001-06-12 11:14 ` Thomas Sailer
2001-06-12 14:35 ` David Brownell [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=marc-linux-hotplug-99235670124629@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).