Typedefs | |
typedef enum svn_wc_notify_action_t | svn_wc_notify_action_t |
The type of action occurring. | |
typedef enum svn_wc_notify_state_t | svn_wc_notify_state_t |
The type of notification that is occurring. | |
typedef void(* | svn_wc_notify_func_t )(void *baton, const char *path, svn_wc_notify_action_t action, svn_node_kind_t kind, const char *mime_type, svn_wc_notify_state_t content_state, svn_wc_notify_state_t prop_state, svn_revnum_t revision) |
Notify the world that action has happened to path. More... |
These notifications have a standard callback function type, which takes the path of the file that was affected, and a caller- supplied baton.
Note that the callback is a 'void' return -- this is a simple reporting mechanism, rather than an opportunity for the caller to alter the operation of the WC library.
Note also that some of the actions are used across several different Subversion commands. For example, the update actions are also used for checkouts, switches, and merges.
|
Notify the world that action has happened to path. path is either absolute or relative to cwd (i.e., not relative to an anchor). kind, content_state and prop_state are from after action, not before.
If mime_type is non-null, it indicates the mime-type of path. It is always
revision is
Note that if action is ### Design Notes: The purpose of the kind, mime_type, content_state, and prop_state fields is to provide "for free" information that this function is likely to want, and which it would otherwise be forced to deduce via expensive operations such as reading entries and properties. However, if the caller does not have this information, it will simply pass the corresponding `*_unknown' values, and it is up to the implementation how to handle that (i.e., whether or not to attempt deduction, or just to punt and give a less informative notification).
Recommendation: callers of |