[web-team] Fixed (was: modified/unlocked RCS files)

[Heather Stern]

Prevention of the original problem would require evim to stop breaking the
lock badly.

The original problem was generated by the following method:
    I logged in to prepare the second update-note I'd done about
    kernel-study-group-meets.

    I followed the age old directions (that I helped write) to unlock
    the events sidefile.

    I edited it, using vim.  The previous one, I'd tried "evim" as suggested
    by the then-present motd as handling the locks.  It didn't.  That was
    the previous occurrance of the locks problem.  Plain vim should have
    been better.

    I tried to check the file back in.  "no lock set by star." 

    I had someone expecting me to drive someplace, so I checked that the
    file was visible.  We have a team and as long as the file doesn't get
    reverted before the actual kernel meet, the computer won't care (just
    send grumpy notes per its marching orders).

> > If I had to bet how the editing party caused that problem, I'd speculate
> > her having omitted the "-l" (lock) flag during checkout.  Please be
> > careful about that -- and when in doubt, ask help.

If I had to bet that the system has been so horribly maintained that our
directions as written aren't valid, it shouldn't be very high stakes, since
it's an easy bet.

> > There's really not much to it, though:
> > 
> >   co -l  [foo]
> >   (Edit the file.)
> >   ci -u  [foo]
> 
> I assume that the "editing party" is on this mailing list? :-)
> 
> Lisa

Yeah, and she's a billion times easier to reach by phone, but some parties
don't talk to her much these days.  I've lost too many friends this year.

  . | .    Heather Stern          |     (408) 374-7623 land
--->*<---  star at starshine.org   - * -   (408) 761-4912 cell
  ' | `    KG6ZYC                 |