From: Chip Salzenberg <chip@pobox.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: nfs@lists.sourceforge.net
Subject: Re: New version of nfs-utils please!
Date: Fri, 12 Sep 2003 13:02:07 -0400 [thread overview]
Message-ID: <20030912170207.GA28213@perlsupport.com> (raw)
In-Reply-To: <16225.27552.308538.665130@notabene.cse.unsw.edu.au>
According to Neil Brown:
> I've just fixed the reported 'statd segfaults' problem.
Cool beans. Really a glibc bug from the description, isn't it?
> If you would like to make any appropriate changes to ChangeLog and
> debian/* to reflect the new version number ...
Done! Thanks.
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-09-12 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 15:31 New version of nfs-utils please! Chip Salzenberg
2003-09-12 6:45 ` Neil Brown
2003-09-12 17:02 ` Chip Salzenberg [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=20030912170207.GA28213@perlsupport.com \
--to=chip@pobox.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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