Searched refs:T_MODIFIED (Results 1 – 10 of 10) sorted by relevance
294 status = T_MODIFIED; in find_fileproc()738 if (status == T_UPTODATE || status == T_MODIFIED || in classify_file_internal()747 status = T_MODIFIED; in classify_file_internal()748 else if (status == T_MODIFIED && xstatus == T_CONFLICT) in classify_file_internal()749 status = T_MODIFIED; in classify_file_internal()779 status = T_MODIFIED; in classify_file_internal()843 status = T_MODIFIED; in check_fileproc()854 case T_MODIFIED: in check_fileproc()883 if (status == T_MODIFIED && vers->tag && in check_fileproc()899 if (status == T_MODIFIED && !force_ci && file_has_markers (finfo)) in check_fileproc()[all …]
323 ret = T_MODIFIED; in Classify_File()334 ret = T_MODIFIED; in Classify_File()
182 case T_MODIFIED: in status_fileproc()
823 T_MODIFIED, /* M (needs checked in) list */ enumerator
71 type = T_MODIFIED; in setup_tmpfile()
673 case T_MODIFIED: /* locally modified */ in update_fileproc()707 case T_MODIFIED: /* locally modified */ in update_fileproc()
628 case T_MODIFIED: in check_fileproc()
2918 T_MODIFIED even if the file hasn't changed.3055 T_MODIFIED and ts_conflict set, so that it doesn't say "unresolved
1194 status is T_MODIFIED, require that finfo->rcs be set, call
110 how T_MODIFIED could later turn out to have conflict markers and why115 T_MODIFIED, since force could be requested. Simplify logic since