|
|
| Author |
Message |
| 20 new of 64 responses total. |
aruba
|
|
response 45 of 64:
| 
Jan 25 00:46 UTC 2000 |
Thanks Mary, for doing that legwork.
|
mary
|
|
response 46 of 64:
|
Jan 25 00:51 UTC 2000 |
You're welcome.
|
gypsi
|
|
response 47 of 64:
|
Jan 25 13:50 UTC 2000 |
Thank you, Mary. It sounds like it went well. =)
|
eeyore
|
|
response 48 of 64:
|
Jan 25 15:58 UTC 2000 |
Thankyou very much, Mary!!! :)
|
swa
|
|
response 49 of 64:
|
Jan 26 05:48 UTC 2000 |
Who or what is baff, if I may inquire?
|
gelinas
|
|
response 50 of 64:
|
Jan 26 06:47 UTC 2000 |
It's an e-mail alias for:
valerie, remmers, grex@gibbard.org, srw, steve,
gregc, mdw@umich.edu, nephi, scott, janc, kaplan,
dang, other, eeyore, flem
Some of these I recognise, others I don't. Nor have I deciphered the
acronym.
|
scg
|
|
response 51 of 64:
|
Jan 26 07:37 UTC 2000 |
It's a combination of the board and staff mailing lists.
|
spooked
|
|
response 52 of 64:
|
Jan 26 08:53 UTC 2000 |
Except it's not a conclusive list. I should be on it, and probably one or
two others.
|
other
|
|
response 53 of 64:
|
Jan 27 03:33 UTC 2000 |
you should have appropriate access to update that list, mic.
|
scg
|
|
response 54 of 64:
|
Jan 27 03:50 UTC 2000 |
Yup.
rcsdiff /etc/aliases
if that shows there being no differences between the checked in and checked
out copies
co -l /etc/aliases
vi /etc/aliases
ci -u /etc/aliases
newaliases
else
vi /etc/aliases
newaliases
|
gelinas
|
|
response 55 of 64:
|
Jan 27 04:12 UTC 2000 |
<drift>
Is there a reason to leave the aliases file locked by someone else after
editing it? Wouldn't it make more sense to break the lock and then check
it back in?
</drift>
|
scg
|
|
response 56 of 64:
|
Jan 27 04:23 UTC 2000 |
Probably, except that it would just get left checked out again within the next
few days anyway. The right answer would be to stop using RCS on that file.
|
other
|
|
response 57 of 64:
|
Jan 27 05:08 UTC 2000 |
umm. what is RCS?
and what means "checking out/in" a file?
|
spooked
|
|
response 58 of 64:
|
Jan 27 05:42 UTC 2000 |
RCS = Revision Control System. It's a package which allows maintenance of
file revisions. Often useful in programming to not lose working versions,
or just generally to backtrack - see who modified a file, etc.
I've never used it before myself, but it seems easy enough (I'll have a quick
read of the chapter on it in one of my Unix books sometime).
|
gelinas
|
|
response 59 of 64:
|
Jan 27 06:33 UTC 2000 |
Eric, the short form is: read the man pages on rcs, ci and co.
|
other
|
|
response 60 of 64:
|
Jan 28 03:38 UTC 2000 |
wow. seems like a simple concept with a terribly complex description.
|
gelinas
|
|
response 61 of 64:
|
Jan 28 03:41 UTC 2000 |
That's why I sent you to the man pages, rather than try to describe it myself.
|
other
|
|
response 62 of 64:
|
Jan 28 03:51 UTC 2000 |
<grin> good call!
|
davel
|
|
response 63 of 64:
|
Jan 29 13:41 UTC 2000 |
It's terribly easy to check in a file, forgetting to use the option that
causes it to leave the file in existence (outside the RCS database).
Embarrassing.
|
gelinas
|
|
response 64 of 64:
|
Jan 29 21:28 UTC 2000 |
Yeah, it is. Fortunately, I'm more likely to forget the file name than the
minusU option.
|