Date: Mon, 6 Oct 1997 22:40:26 -0500 From: Richard Wackerbarth <rkw@dataplex.net> To: Chris Dillon <cdillon@tri-lakes.net> Cc: stable@freebsd.org Subject: Re: Fwd: CVSup release identity Message-ID: <l03110700b05f5be4dc14@[208.2.87.4]> In-Reply-To: <XFMail.971006221828.cdillon@tri-lakes.net> References: <l0311070bb05e8b80e634@[208.2.87.4]>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Dillon <cdillon@tri-lakes.net> writes: >Yes. For those that use cvsup, cvsupd could pass the timestamp to >the client using the local time of the master server (therefore avoiding >problems cropping up from incorrect local times). Remember that the cvsupd that YOU contact is NOT the master server. The stamp would need to be inserted ONLY when transferring from the master server. All other distribution systems, including the publicly accessable cvsupd servers and ctm would simply propogate the designation that they receive. This could be most readily done by having it as a string in a file. >>The only objection ... may not be "user friendly". I guess we could do the following: Before release: 2.2 (9710061501) At release: 2.2.0 (RELEASE) After release: 2.2.0 (9710061703) Another Release: 2.2.2 (RELEASE) And then: 2.2.2 (9710061905) That way, anything other than a release would have a timestamp and the number of the previous release from which it was derived. Richard Wackerbarth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?l03110700b05f5be4dc14>