From: Denis Vlasenko <vda.linux@googlemail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Dave Jones <davej@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: futex hang with rpm in 2.6.17.1-2174_FC5
Date: Mon, 27 Nov 2006 01:02:50 +0100 [thread overview]
Message-ID: <200611270102.50218.vda.linux@googlemail.com> (raw)
In-Reply-To: <453A622C.2020401@candelatech.com>
On Saturday 21 October 2006 20:08, Ben Greear wrote:
> > > or shouldn't rpm notice the previous process is dead and
> > > clean it up itself?
> >
> > Sounds sensible to me and you, but in the past sensible ideas and
> > rpm maintainers haven't gone hand in hand.
> >
> Ahhh :)
Well said. rpm's source tarball size doubles with each release
and it contains such unexpected things as ELF manipulation
library. I have no idea what business rpm can possibly have with
parsing ELF headers.
--
vda
prev parent reply other threads:[~2006-11-27 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 18:38 futex hang with rpm in 2.6.17.1-2174_FC5 Ben Greear
2006-10-21 5:24 ` Dave Jones
2006-10-21 17:45 ` Ben Greear
2006-10-21 18:00 ` Dave Jones
2006-10-21 18:08 ` Ben Greear
2006-10-21 21:55 ` Ulrich Drepper
2006-11-27 0:02 ` Denis Vlasenko [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=200611270102.50218.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=davej@redhat.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.