." ." Copyright (c) 1991 by Sun Microsystems, Inc. ." ." @(#)notification.4 1.4 92/04/24 SMI ." .TH NOTIFICATION 4 "00/03/28 Sun WorkShop 6" .SH NAME notification \- TeamWare notification file .SH SYNOPSIS .B Codemgr_wsdata/notification .LP .SH DESCRIPTION The \fBnotification\fP file registers notification requests. The notification facility permits TeamWare commands to detect TeamWare events that involve a workspace and to send electronic mail in response to the event. The following are the events that can be registered: .IP bringover-from .sp 0 bringover-to .sp 0 putback-from .sp 0 putback-to .sp 0 undo .sp 0 workspace-delete .sp 0 workspace-move .sp 0 workspace-reparent .sp 0 workspace-reparent-to .LP Whenever a user creates a workspace, a default notification file is created in the .B Codemgr_wsdata metadata directory. The default file consists of a large comment that describes the format of the file (the "#" character at the beginning of a line delimits a comment). Users can modify the notification file through the Workspace > Properties > Notification dialog box, or edit this file directly. .B .LP The following is a copy of the default notification file. It describes the format of the file. .sp .nf VERSION 1 # # A workspace's notification file. # # Note: Because this file is edited manually, you may # want to maintain it using SCCS. # # The format for each entry is: # # email_address event ... # BEGIN # file1 # dir # . # . # . # END # # where is the address to which the mail will be sent; # is one of the following: # bringover-from # bringover-to # putback-from # putback-to # undo # workspace-delete # workspace-move # workspace-reparent # workspace-reparent-to # # The bringover, putback, and undo events can include a list of files and # directories to be associated with the event. When a directory is listed, # all files hierarchically beneath it are registered. The list must be # delimited by BEGIN and END statements. To get registration for all files # in the workspace, use a list of ".", an empty list, or no list. # # The following is a sample notification file: # # chip@mach1 bringover-to # BEGIN # dir/foo.cc # dir/bar.cc # END # biff@mach2 bringover-to putback-to # BEGIN # . # END # biff@mach2 workspace-move # .fi .LP In the sample notification file above, the first entry causes mail to be sent to .B chip whenever a user brings over the files .B dir/foo.cc and .B dir/bar.cc into the workspace. The second entry causes mail to be sent to .B biff whenever a user brings over or puts back .I any files into the workspace. The third entry causes mail to be sent to .B biff when the workspace is moved. .LP .in -5 .SH "SEE ALSO" .IR "Sun WorkShop TeamWare User's Guide" .LP .sp .nf bringover(1), codemgr(1), def.dir.flp(1), dmake(1), freezept(1), putback(1), rcs2ws(1), resolve(1), teamware(1), twbuild(1), twfreeze(1), twmerge(1), twversion(1), workspace(1), ws_undo(1), access_control(4), args(4), children(4), conflicts(4), description(4), freezepointfile(4), history(4), locks(4), nametable(4), parent(4), putback.cmt(4)