From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Jeff Bailey <jbailey@nisa.net>
Cc: debian-glibc@lists.debian.org, parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] glibc 2.3.2 hppa - Requires Rminkernel patch to catch < 2.4.17 users.
Date: Wed, 22 Oct 2003 00:32:27 -0400 [thread overview]
Message-ID: <20031022043227.GD20912@systemhalted> (raw)
Jeff,
glibc-package/debian/patches/glibc23-hppa-Rminkernel.dpatch
Has to go back into the list of patches, since it will keep users
running their boxes with 2.4.17 or later based kernels instead of
2.4.19. Developer testing didn't catch this since we all run >2.4.19.
Please and thank you!
I'm doing the patches for the -rnptl branch right now, if I had paid
attention I would have tried harder to queue this up earlier so it could
have gone out on the recent release.
c.
next reply other threads:[~2003-10-22 4:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 4:32 Carlos O'Donell [this message]
2003-10-22 14:15 ` [parisc-linux] Re: glibc 2.3.2 hppa - Requires Rminkernel patch to catch < 2.4.17 users Jeff Bailey
2003-10-22 14:15 ` Jeff Bailey
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 4:32 [parisc-linux] " Carlos O'Donell
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=20031022043227.GD20912@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=debian-glibc@lists.debian.org \
--cc=jbailey@nisa.net \
--cc=parisc-linux@lists.parisc-linux.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.