From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: * X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,791530e499e6a7f9 X-Google-Attributes: gid103376,public From: Ted Dennison Subject: Re: ada writing guide Date: 2000/04/19 Message-ID: <8dke9a$hc1$1@nnrp1.deja.com>#1/1 X-Deja-AN: 613133022 References: <8d1rso$bir$2@bunyip.cc.uq.edu.au> <8d1vhj$hdr$1@nnrp1.deja.com> <8d2hig$7e6$1@nnrp1.deja.com> <38F5DF8C.1A01E5A4@utech.net> <8d4t07$o15$1@nnrp1.deja.com> <38F603FE.B0C3ED83@utech.net> <8d5dsc$c27$1@nnrp1.deja.com> <8d6hjn$j9p$1@clnews.edf.fr> <8d76vj$9jt$1@nnrp1.deja.com> <8d7uak$1d1$1@wanadoo.fr> <8dfd6q$uch$1@nnrp1.deja.com> <87em84vavt.fsf@deneb.cygnus.argh.org> <8dfpj7$crs$1@nnrp1.deja.com> <8dgk8i$ak4$1@nnrp1.deja.com> <8dhqi7$jv3$1@nnrp1.deja.com> <8dhuuu$ou5$1@nnrp1.deja.com> <8di8da$4el$1@nnrp1.deja.com> <874s8yeg81.fsf@deneb.cygnus.argh.org> X-Http-Proxy: 1.0 x33.deja.com:80 (Squid/1.1.22) for client 204.48.27.130 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Wed Apr 19 14:02:29 2000 GMT X-MyDeja-Info: XMYDJUIDtedennison Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.7 [en] (WinNT; I) Date: 2000-04-19T00:00:00+00:00 List-Id: In article <874s8yeg81.fsf@deneb.cygnus.argh.org>, Florian Weimer wrote: > Ted Dennison writes: > > > No warnings are given, no backups are made. The old version is > > over-written. Even for those who know the danger, this would be easy to > > accidentally do. > > This can't happen with systems like CVS where each user works on his > private copy of the source files. The master files are often not > directly accessible. Problem solved. ;) Hmm. I use CVS at home, but I guess that's not multiuser (yet, perhaps It'll be that way when my kids are older :-) ). I'm still not convinced CVS wouldn't have the problem too. But at least the process give you one hint. I see it working this way. User A does a "cvs checkout" of the repository User B does a "cvs checkout" of the repository User A starts up emacs (which reads the exception file into memory). User B starts up emacs (which reads the exception file into memory). User A hits Ctrl-C Ctrl-Y User A does a "cvs commit" on the exception file User B finds out there were changes, and does a "cvs update" User B hits Ctrl-C Ctrl-Y (unknowingly wiping out user A's changes) User B does a "cvs commit" At least this way, there is a manual updating step in there, where the wise user could say, "I'd better bring my emacs up to date, just to be safe." But it'd still be awfully easy to forget, or overlook a running session somewhere. -- T.E.D. http://www.telepath.com/~dennison/Ted/TED.html Sent via Deja.com http://www.deja.com/ Before you buy.