# # # patch "NEWS" # from [073fce5a18909977325ac839f297708eefbd175b] # to [4bba5bf4705a3933a63c0ceb9e7e2269c95fdb94] # # patch "monotone.texi" # from [8f8983c5d6ae2706aa410b6520c572c746d0966c] # to [ca97852a0e561fda1dcdd5e11f838c91cadd87c9] # ============================================================ --- NEWS 073fce5a18909977325ac839f297708eefbd175b +++ NEWS 4bba5bf4705a3933a63c0ceb9e7e2269c95fdb94 @@ -83,9 +83,12 @@ Xxx Xxx 99 99:99:99 UTC 2010 New Features - - the 'disapprove' command now accepts a revision range in + - The 'disapprove' command now accepts a revision range in addition to a single revision. + - New 'k:' selector type to query revisions where at least one + certificate was signed with the given key. + - New automation command 'log' which behaves identical to the normal 'log' command, except that it only outputs the revision ids. ============================================================ --- monotone.texi 8f8983c5d6ae2706aa410b6520c572c746d0966c +++ monotone.texi ca97852a0e561fda1dcdd5e11f838c91cadd87c9 @@ -1068,10 +1068,10 @@ @subsection Branch Names It has to be noted that earlier versions of monotone enforced no restrictions on branch names. Newer versions, starting with 0.99, exclude a set of control -characters though, which mostly denote either meta characters in monotone's +characters though, which mostly denote either meta characters in monotone's URI syntax or are used in globs to resolve branch patterns. These characters are @code{?}, @code{,}, @code{*}, @code{%}, @code{+}, @address@hidden, @address@hidden, @code{[}, address@hidden, @code{!} and @code{^}. Additionally, @code{-} is deprecated as first address@hidden, @code{!} and @code{^}. Additionally, @code{-} is deprecated as first character of a branch name, since it is used to denote branch exclude patterns in the aforementioned URI syntax. @@ -2814,6 +2814,11 @@ @heading Selectors in detail @item Author selection Uses selector type @code{a}. For example, @code{a:graydon} matches @code{author} certs where the cert value contains @code{graydon}. address@hidden Key selection +Uses selector type @code{k}. For example, @code{k:graydon@@pobox.com} matches +all revisions where at least one cert was signed by the key address@hidden@@pobox.com}. Instead of the key's given name, the local +name or the full hash ID of the key can be specified as well. @item Branch selection Uses selector type @code{b}. For example, @code{b:net.venge.monotone} matches @code{branch} certs where the cert value is @code{net.venge.monotone}. @@ -3751,7 +3756,7 @@ @heading Existing vars @item server-include Contains server-specific branch inclusion globs. These overrule @var{default-include-pattern} if existant and are recorded automatically -the first time you connect to a specific server or use the +the first time you connect to a specific server or use the @option{--set-default} option for a netsync operation. @item server-exclude @@ -5756,9 +5761,9 @@ @section Network databases. The @command{pull}, @command{push}, and @command{sync} commands only -require you pass @var{uri} (or @var{address} and @var{glob}) the first time +require you pass @var{uri} (or @var{address} and @var{glob}) the first time you use one of them; monotone will memorize this use and in the future default -to the same URI (or server and glob). For instance, if Bob wants to +to the same URI (or server and glob). For instance, if Bob wants to @command{sync} with Alice again, he can simply run: @smallexample @@ -5783,7 +5788,7 @@ @section Network identifier of the server in the file. This file can then be read to identify specific monotone server processes. -The syntax for patterns, both in globs as well as URIs, is very simple. +The syntax for patterns, both in globs as well as URIs, is very simple. @code{*} matches 0 or more arbitrary characters. @code{?} matches exactly 1 arbitrary character (you need to escape that with @code{%3F} in an URI). @address@hidden,bar,address@hidden matches ``foo'', or ``bar'', or ``baz''. These