From: Chip Salzenberg <chip@pobox.com>
To: gmorris@users.sourceforge.net
Cc: nfs@lists.sourceforge.net
Subject: Resent: Please document change log entry for support/nfs/cacheio.c
Date: Thu, 10 Mar 2005 13:29:25 -0500 [thread overview]
Message-ID: <20050310182925.GE4577@perlsupport.com> (raw)
Your recent change to support/nfs/cacheio.c has no ChangeLog entry.
Likewise your change to exports.man. Would you be so kind as to add
entries to ChangeLog for these changes?
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
Open Source is not an excuse to write fun code
then leave the actual work to others.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-03-10 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 18:29 Chip Salzenberg [this message]
2005-03-11 6:35 ` Resent: Please document change log entry for support/nfs/cacheio.c G. Allen Morris III
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=20050310182925.GE4577@perlsupport.com \
--to=chip@pobox.com \
--cc=gmorris@users.sourceforge.net \
--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 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.