| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Broken-by: e2ff8e24f4
|
|
|
|
|
|
|
|
domain. Bug 2375
|
|
(cherry picked from commit c5c57c4eafde32a0632c2a00bdc634860fc5d06d)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(Closes 2171)
Better yet would be to force setting the output separator literally,
and not after expansion of the STRING. But this would be an incompatible
change.
|
|
|
|
|
|
|
|
|
|
queue_run_max main option expanded, allowing per-queue values
|
|
|
|
|
|
Broken-by: 82dbd37
In "skipping" mode when parsing an expansion we want to avoid expanding
the arguments, as the data for expansion is not necessarily valid. This
bit us previously for an extract within an "if inlist". But the number of
args for ${extract } depends on the expanded value of the first arg.
Retreat from strict parsing and just line up the outer braces,
accepting any number of args while skipping. The separate
non-skipping execution will do the proper checking.
|
|
|
|
|
|
Bug 1650
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fix conditional "bool{<string>}" for negative number values, to match.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
