search for: report_exclude_result

Displaying 6 results from an estimated 6 matches for "report_exclude_result".

2003 Feb 16
1
rsync-exclude.patch.
...unless the default list is cleared with "!", it automatically excludes *.a and *.so libraries). diff -ru rsync-2.5.6/exclude.c rsync-2.5.6J/exclude.c --- rsync-2.5.6/exclude.c Sun Jan 26 13:10:23 2003 +++ rsync-2.5.6J/exclude.c Wed Jan 29 17:16:39 2003 @@ -127,6 +127,7 @@ static void report_exclude_result(char const *name, struct exclude_struct const *ent, + char const *type, STRUCT_STAT const *st) { /* If a trailing slash is present to match only directories, @@ -134,10 +135,10 @@ * case we add it back in...
2003 Jan 14
3
.rsync-/.rsync+ patch and --link-dest example
This is a patch to add an --rsync-exclude option to rsync-2.5.6cvs. File names in .rsync- (or .rsync+) are excluded (or included) from the file lists associated with the current directory and all of its subdirectories. This has advantages over --cvs-exclude for backing up large file systems since the .cvsignore files only apply to the current directory: unless the .cvsignore restrictions apply
2004 Apr 09
3
include/exclude bug in rsync 2.6.0/2.6.1pre1
...of code in 2.5.7, the behaviour is different (in the case of an included pattern, local_exclude list is not examined): if (exclude_list) { for (n=0; exclude_list[n]; n++) { ent = exclude_list[n]; if (check_one_exclude(name, ent, st)) { report_exclude_result(name, ent, st); return !ent->include; } } } if (local_exclude_list) { for (n=0; local_exclude_list[n]; n++) { ent = local_exclude_list[n]; if (check_one_exclude(name, ent, st)) { report_ex...
2002 May 22
1
rsyncd listing of directories
...to make the list_only (remote file list) more useful */ if (list_only && !recurse) argstr[x++] = 'r'; in exclude.c: /* This is a complete hack - blame Rusty. * * FIXME: This pattern shows up in the output of * report_exclude_result(), which is not ideal. */ if (list_only && !recurse) { add_exclude("/*/*", 0); } So I'm going to bite and blame Rusty at this point and ask the question: why was this implemented this way? I can't think of a good reason why. I'm ha...
2004 Jan 27
1
Differentiating debug messages from both sides
...3,7 @@ void free_exclude_list(struct exclude_st struct exclude_struct **list = *listp; if (verbose > 2) - rprintf(FINFO,"clearing exclude list\n"); + rprintf(FINFO, "[%c] clearing exclude list\n", *who_am_i); if (!list) return; @@ -203,12 +204,14 @@ static void report_exclude_result(char c * then it is stripped out by make_exclude. So as a special * case we add it back in here. */ - if (verbose >= 2) - rprintf(FINFO, "%s %s %s because of pattern %s%s\n", + if (verbose >= 2) { + rprintf(FINFO, "[%c] %s %s %s because of pattern %s%s\n", + *...
2002 Nov 11
0
Regular Expression support
...r(name,'/'))) name = p+1; @@ -106,7 +187,7 @@ pattern++; } - if (ex->regular_exp) { + if (ex->fnmatch) { if (fnmatch(pattern, name, ex->fnmatch_flags) == 0) { return 1; } @@ -119,11 +200,11 @@ return 1; } } + } return 0; } - static void report_exclude_result(char const *name, struct exclude_struct const *ent, STRUCT_STAT const *st) @@ -179,7 +260,7 @@ } -void add_exclude_list(const char *pattern, struct exclude_struct ***list, int include) +void add_exclude_list(const char *patt...