Home
last modified time | relevance | path

Searched refs:patterns (Results 1 – 5 of 5) sorted by relevance

/coreutils/src/
Dshred.c675 patterns[] = variable
713 p = patterns; in genpattern()
723 p = patterns; in genpattern()
Ddircolors.hin17 # Below are TERM or COLORTERM entries, which can be glob patterns, which
Dls.c3176 patterns_match (struct ignore_pattern const *patterns, char const *file) in patterns_match() argument
3179 for (p = patterns; p; p = p->next) in patterns_match()
/coreutils/
DNEWS134 split now uses more tuned access patterns for its potentially large input.
1364 shred again uses defined patterns for all iteration counts.
4822 du's --exclude-from=FILE and --exclude=P options now compare patterns
/coreutils/doc/
Dcoreutils.texi3597 are not matched in subsequent regexp patterns.
10583 with data patterns chosen to
10585 By default the patterns are designed for best effect on hard drives using
10629 appropriate. After 25 passes all of the internal overwrite patterns will have
12761 Like @option{--exclude}, except take the patterns to exclude from @var{file},
12762 one per line. If @var{file} is @samp{-}, take the patterns from standard
14024 @cindex matching patterns