Date: Tue, 27 Dec 2011 13:00:15 +0000 From: Chris Rees <crees@freebsd.org> To: "Julian H. Stacey" <jhs@berklix.com> Cc: "ctm-users@freebsd.org" <ctm-users@freebsd.org> Subject: Re: svn-cur Message-ID: <CADLo838PROzusosLJO1OKjPe=QzLG0CxrzSUnTCtxt0DtypJew@mail.gmail.com> In-Reply-To: <201112271237.pBRCbooj079986@fire.js.berklix.net> References: <4EF92876.2080508@missouri.edu> <201112271237.pBRCbooj079986@fire.js.berklix.net>
index | next in thread | previous in thread | raw e-mail
On 27 December 2011 12:37, Julian H. Stacey <jhs@berklix.com> wrote: > Hi Stephen >> On 12/26/2011 07:55 PM, Julian H. Stacey wrote: >> >> Suggestion: >> >> Maybe you might want a 5 digit numeric, not 4 digit, like cvs-cur ? >> >> (as eg there's often more cvs deltas than other deltas) >> > >> > Suggestion: >> > Also use same convention as before in naming with xEmpty to indicate a base >> > ctm (delta) rather than just a differential ctm (delta). >> > mv svn-cur.0001.xz svn-cur.00001xEmpty.xz >> > mv svn-cur.0002.xz svn-cur.00002.xz >> >> The convention that svn-cur.0001 does not have xEmpty in it is a >> convention that has been followed before. Look at src-9. It is how the >> mkCTM software works. > > OK, thanks, I had wondered if it was a mistake. > I hadn't noticed the example of src-9 till now. > > The name 'Empty' was a useful marker to distinguish & seperate a > full from a differential file.... We're now up to src-9.0077.gz > > Question: > Might there may be trouble when we get to src-9.0100.gz ? > A double bid for that file name: > - Recipient hosts will want a normal small incremental update. > - Sender & ftp mirror servers, that same name needs to hold > 2 different sets of content, > - for a differential. > - for a complete archive > How will ctm recipients later distinguish which CTM delta to pull via ftp > if they both have the same name ? eg > src-9.0300.gz a complete base CTM archive for later starters > src-9.0300.gz a differential delta for those ftp'ing after > maybe a mail outage on recipient loses an odd delta. > Using same name in different new directories might also be problematic, as > if we had eg > /pub/FreeBSD/development/CTM/src-cur/src-9.0101.gz > /pub/FreeBSD/development/CTM/src-cur/empty-new-dir/src-9.0101.gz > all mirror site would need to create directories called /empty-new-dir/ > which might (I don't know) require permission/manual intervention on mirrors). > > The scenario I guess hasn't happened before, & doesn't matter when a new > archive first starts, as per src-9.0001.gz, > but I guess this potential problem approaches as src-9.0077.gz > approaches src-9.0100.gz or src-9.0101.gz ? > Stephen is pointing out that src-9.0001 is not an incremental delta; there's no src-9.0000. Yes, when it gets to src-9.0100 there'll be an Empty file here, but since there's no difference between 0001 and 0001Empty, there's no point in having both files there. Chrishome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo838PROzusosLJO1OKjPe=QzLG0CxrzSUnTCtxt0DtypJew>