Hello,
In looking at the potential for a ``quiet mode for update'' I wondered
if this might already be possible by simply using TH1 hooks, but then I
realized I don't know much about TH1 hooks except that they can be used
to do things prior to executing a certain command; but what things
Thus said David Mason on Thu, 02 Oct 2014 09:35:50 -0400:
I want a script to run every 5 minutes and if there is any update,
email me the update log. But I don't want email every 5 minutes that
just says everything is up to date.
After thinking about it a bit more, I realized all
Thus said Andy Bradford on 07 Oct 2014 00:21:48 -0600:
fossil sync /dev/null fossil update -n | grep '^changes:' | grep -v
'None. Already up-to-date' {
fossil update 21 | mail -s 'Fossil update' m...@he.re
}
Perhaps something that matches a positive would be better:
fossil sync
On 7 October 2014 02:30, Andy Bradford
amb-sendok-1415255446.lmkmojimnoldkcbjb...@bradfords.org wrote:
fossil sync /dev/null fossil update -n | grep '^changes:.*files
modified\.' {
fossil update 21 | mail -s 'Fossil update' m...@he.re
}
Best yet, although you actually want a -q switch on
Andy Bradford wrote:
If Iconfigure the FOSSIL_ENABLE_TH1_HOOKS(e.g. configure
--with-th1-hooks) what does that get me? I assume from the code that it
will call Th_CommandHook passing in the name and flags, but to what in
the TH1 environment? My guess is that I need a
On Tue, Oct 7, 2014 at 12:06 PM, Joe Mistachkin sql...@mistachkin.com
wrote:
Then, you would normally need a th1-setup script, set via the settings
command or a .fossil-settings file. There would need to be a procedure
defined named command_hook (and/or command_notify), e.g.:
proc
Ron W wrote:
What's in $::cmd_args ? Is it just the command line (or command URL)?
The command line arguments, just as they existed in the g.argv field at
that point. It should be noted that the command line arguments _cannot_
currently be modified by the hook, only inspected.
In
7 matches
Mail list logo
