From: Paul Franklin <paul@cs.washington.edu>
Subject: Re: new back-end interface to fix article move/delete problems
Date: 12 Feb 1997 00:56:20 -0800 [thread overview]
Message-ID: <r9q914ujtcb.fsf@fester.cs.washington.edu> (raw)
In-Reply-To: Joe Wells's message of 10 Feb 1997 23:32:26 -0500
>>>>> Joe Wells writes:
> A reasonable restriction of the proposed back-end-interface would be to
> require that a non-existing article number must be one that the article
> used earlier that has since been deleted. This would support goal 1 but
> not goal 2. It would also probably avoid the problems that Paul
> envisioned.
Yup. I would also be perfectly happy with the lesser restriction that
it be less than the highest known article number (specified in the
active file), since I'm only worried about articles which might exist
above that highest known article number.
I just didn't want someone to decide to supply 1 more than the last
number in the active file because "I know what article number the
backend would use."
--Paul
prev parent reply other threads:[~1997-02-12 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-24 4:03 Joe Wells
1997-02-05 7:01 ` Paul Franklin
1997-02-11 4:32 ` Joe Wells
1997-02-12 8:56 ` Paul Franklin [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=r9q914ujtcb.fsf@fester.cs.washington.edu \
--to=paul@cs.washington.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).