From: Nevin Kapur <nevin@jhu.edu>
Subject: Re: [PATCH] Expiry based on headers (Take 2)
Date: Sat, 08 Dec 2001 18:35:19 -0500 [thread overview]
Message-ID: <m3itbhcmko.fsf@bombay.dyndns.org> (raw)
In-Reply-To: <ilur8q5xskb.fsf@dhcp128.extundo.com> (Simon Josefsson's message of "Sat, 08 Dec 2001 23:20:20 +0100")
Simon Josefsson <jas@extundo.com> writes:
> Nevin Kapur <nevin@jhu.edu> writes:
>
>> Here's a revised patch for a header-based expiry function that
>> incorporates all of Simon's suggestion. This is my first attempt at
>> using custom non-trivially, so any correction would be welcome.
>
> I modified it a little, what do you think of this approach? If you
> don't like we'll use yours.
Looks good to me. Thanks for cleaning up the code.
--
Nevin Kapur
nevin@jhu.edu
next prev parent reply other threads:[~2001-12-08 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-08 16:42 [PATCH] Expiry based on headers Nevin Kapur
2001-12-08 17:11 ` Simon Josefsson
2001-12-08 18:56 ` Nevin Kapur
2001-12-08 21:01 ` [PATCH] Expiry based on headers (Take 2) Nevin Kapur
2001-12-08 22:20 ` Simon Josefsson
2001-12-08 23:35 ` Nevin Kapur [this message]
2001-12-09 0:33 ` Simon Josefsson
2001-12-08 23:53 ` Nevin Kapur
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=m3itbhcmko.fsf@bombay.dyndns.org \
--to=nevin@jhu.edu \
/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).