Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTSRV-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Menu
LISTSERV Archives LISTSERV Archives
LSTSRV-L Home LSTSRV-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
VERS8900
From:
Eric Thomas <ERIC@LEPICS>
Reply To:
Revised LISTSERV forum <LSTSRV-L@CEARN>
Date:
Mon, 22 May 89 12:02:04 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (17 lines)
Could someone explain what  this VERS8900 update is, why it  was named in this
way, and  why nobody was  notified, even  after the fact???  LISTSERV excpects
updates to be numbered sequentially, so that 8905 is more recent than 8904 and
older than  8906 (aren't they called  'VERSyymm'?). It also does  not expect a
month of  00, and 0 minus  1 is a negative  number which is not  expected in a
number of  places (hopefully  this doesn't  seem to  have caused  any problem,
apart from  renaming the old  BITEARN NODES  to VERS89-1 which,  hopefully, is
accepted by  CMS). Other software  may have  been affected, perhaps  even more
severely.
 
If there was a REALLY good reason to  do this, and there had better be one, we
should  have been  notified in  advance. I  hope the  BoD members  realize the
impact  this kind  of behaviour  can have  on the  credibility of  the current
EARN-supplied NODUPD files model.
 
  Eric

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV