From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] fxload fix
Date: Tue, 19 Oct 2004 00:14:41 +0000 [thread overview]
Message-ID: <200410181714.41239.david-b@pacbell.net> (raw)
In-Reply-To: <200410182003.56103.fmhess@users.sourceforge.net>
On Monday 18 October 2004 5:03 pm, Frank Mori Hess wrote:
> Hi,
>
> Is fxload unmaintained?
I think all critical bugs that have landed in my mailbox have
gotten fixed within a month or so, but it's not exactly something
I've got much time for (and nobody else seems to commit to it).
> There haven't been any commits in 2 years, and I'm
> noticing a bug report from 3 months ago here
That bug database would seem to be a bit like a bitbucket, eh?
Didn't even know it was in use.
> that fixes the same problem I reported last week (patch attached again).
Hmm, I saw you post of last week and it's in a stack of a few hundred
emails I was hoping to handle soon. Higher priority than some, since
it seemed to actually fix a minor bug (easy workaround) and the fix
was already done!
Hold your horses ... ;)
- Dave
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-10-19 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 0:03 [PATCH] fxload fix Frank Mori Hess
2004-10-19 0:14 ` 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=200410181714.41239.david-b@pacbell.net \
--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).