From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] fossil changes
Date: Wed, 16 Apr 2003 15:38:27 -0400 [thread overview]
Message-ID: <2d5b18ab60b8ab5ae6b8dfc6f84e7ef5@plan9.bell-labs.com> (raw)
Made a bunch of pending fossil changes.
. file - doesn't stop on errors anymore
users - new, hopefully less confusing syntax
who - prints list of users on each connection
fsys name df - prints disk usage
fsys name halt - stops file system activity
fsys name unhalt - resumes file system activity
fsys name sync - wasn't flushing metadata, now is
fsys all - means apply commands to all fsys
fsys main open - reads /active/adm/users by default
All documented in fossilcons(8).
For people running fossil, the only backwards-incompatible
change is that if you have a line
users /active/adm/users
in your fossil startup file (and you probably do),
the command will now fail due to the new users
syntax. However, that won't matter because:
* `.' will ignore the error in the script
* the opening of main will have loaded
/active/adm/users already anyway.
So you can delete the line after you start running
the new one.
Russ
reply other threads:[~2003-04-16 19:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d5b18ab60b8ab5ae6b8dfc6f84e7ef5@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).