[Xcb] SCMS for XCB?

Jim Gettys Jim.Gettys at hp.com
Mon Aug 1 23:50:02 EST 2005

I think almost everyone working on X would like a new SCM.

But which one isn't yet quite clear.

I expect this will become a serious topic of discussion this fall after
the modular release ships.
				- Jim

On Mon, 2005-08-01 at 09:18 -0400, Trevor Woerner wrote:
> On Saturday 30 July 2005 14:46, Barton C Massey wrote:
> > In message <200507301430.31666.xcb506 at vtnet.ca> you wrote:
> > > On Saturday 30 July 2005 13:34, Barton C Massey wrote:
> > > > Also, is a reasonable ASCII repository format a
> > > > requirement?
> > >
> > > Subversion has had support for both ASCII (fsfs) and binary
> > > (Berkley-db) repository formats for a while. Whoever sets up the
> > > repository has always had a choice, although db has been the
> > > default. With the latest release of subversion, 1.2.0, fsfs (i.e.
> > > ASCII) is now the default.
> >
> > AFAIK, fsfs is still a binary format.  Am I confused?
> fsfs stores each revision and each revision's properties as a separate 
> file (0, 1, 2, ...). You can work with these separate files as you 
> would any other file in the system. My understanding is that these 
> files are stored in something called "delta-storage" which means you 
> can open them with a text editor, basically get the gist of what's 
> going on (you can [mostly] "read" them), but don't make any 
> modifications because the meta-information will now be wrong. Btw, the 
> meta information appears to be stored in ASCII.
> The bdb (Berkley DB) backend stored the entire repository into one 
> binary database file. Special tools were needed in order to examine any 
> internals.
> Is that considered ASCII format? I don't know if this would qualify for 
> you. Just because you can read the file doesn't mean it should be 
> modified (in fact it shouldn't be). There is a process for changing a 
> log message after a commit (say, to fix spelling). But usually after a 
> commit has occurred the database shouldn't be touched.
> I guess we've ended up in this funny state: basic usage of CVS required 
> us to be able to muck around in the repository internals because of all 
> of CVS's shortcomings. Now we've come to expect to be able to muck 
> around in the guts of a r.JǷ[qEf륾C3$!01]qs1z:
-b䁷 Jh@ a!CX֑(bBHy
%1"y˫V]5'(6S#n"@ÖÔ-IESPnDqb>/OC|qAG"Oԗn+e^U/?6je{\ӊn._yuiRDS@M_C!_'S>Yݪcy2ZXakcaXp312BʢF\~IÜ$3uo(""gb󮴼UG.!]蜜wMuhȥ;QYm\UY[V]-}b7wWFr8*S̜/ J u:/%wHQ.(]x%ɾc}3'vu_Iٿ%V1	* l>z[j>uܜdV7PC;,:yjߪz5B	1X]ceUDwj	2)̾,LU&=bunO%^C%*1CTΘa
QwܚUa6C_@ؕАr>ۦeBC&iprB:zpPG#xV<-yQQ	?!=23
(T|بsH2,->^BgOlxO=ܞLM) YCP
[s^FsO$D3< 0yxO`1p|'3I;{3g
4*s6ٓVy0ih^Ty)JSu0TiTiG\	Stwn J8,=|K]	~fmrOIޘ'sg(6[2V7J+pECrv4
,Vt]w{\Ű[Cx3z#i2f6)wxdSvk~;a>,a&T	A87h-oeNfTAh"߄I$-$r&%Rpd8w`駾Cxj	 #ʁtxz_^rzDM<gg~;0K҆L쐄,2!2Icc7- KJr\wd$ zR㞫sKCB7jߏgu5‘*`:]x!0% ɯ%۹J>KZ1-j}beLSKoeЃ7'ϗwXMP,x9[{zTDDڌ ̺ƪE["}wǫ~T"d
J$I"HMֽy^dp	X!P'8ϣ{
@يp#uU73=t/d7-*gFevv\	<*j=H!"SJBT[&G9T{5-K&1AhqcHyG]="^6&
M\4'!I5VE,ATq%7n_5edjxo\.sVk[崦-d8zɃv#HD *°r=07]զ\4yn'q[޼L-V(̒ƈ~	qwQ͍٧\ܭuZ#hxC-{9
_62<2C׶E.tx;+*9Q<=%h	&C:6\~$oB?rZ31c$#?A2mN -
2ӴJߗ1m.n̜| IgUjXJUuqf*#]}*T2Qd<]'/0
$E$ڄ@^!e/e`w`xW	֑ހ-Z:,t9Ӡe,
v6H*T&m| Xoa1
.1—|MoG @v$:UmeR>L7|o
~N5óI1&#!g%T`DxBMKj8q&Ы)y2ri0';oTCz=EM}n3OQo?9\9?@p_#sw̮B RD2#"FK$\wNۯc{kcxjWYijuǸ\7U,f\JMDnϳNfLN