Searched refs:hardlinks (Results 1 – 9 of 9) sorted by relevance
95 hardlinks105 `hardlinks' field contains a list of filenames to which the current108 or eight-bit characters, the filenames in the hardlinks field will111 hardlinks README @install.txt@ @Installation Notes@;113 The hardlinks field should always include the name of the current114 file. That is, in the repository file README,v, any hardlinks fields
857 * RCSFILES: Updated description of `hardlinks' newphrases.868 * cvs.texinfo (Editing files, Special Files): Document hardlinks.
161 List *hardlinks; member
17346 hardlinks)17353 dotest hardlinks-1 "${testcvs} -q co -l ." ''17355 dotest hardlinks-2 "${testcvs} add first-dir" \17364 pass hardlinks-2.117366 fail hardlinks-2.117371 pass hardlinks-2.217373 fail hardlinks-2.217378 pass hardlinks-2.317380 fail hardlinks-2.317383 dotest hardlinks-3 "${testcvs} add [abd]*" \[all …]
1660 * sanity.sh (perms symlinks symlinks2 hardlinks): Don't run by4316 * sanity.sh (hardlinks): Remove comment about spurious warnings;4326 (getdelta): Call them, storing `hardlinks' field in vnode->hardlinks.4331 * sanity.sh (hardlinks): Use uglier filenames. Checking out4334 (hardlinks-2.3): Renamed from hardlinks-2.2 (duplicate test name).4340 member `hardlinks'.4341 * update.c (special_file_mismatch): Get hardlinks from4342 vp->hardlinks instead of from vp->other_delta.4343 * rcs.c (free_rcsvers_contents): Comment about freeing hardlinks4345 (RCS_checkout) [PRESERVE_PERMISSIONS_SUPPORT]: Get hardlinks from[all …]
4208 List *links = vers->hardlinks;5000 delta->hardlinks = list_linked_files_on_disk (workfile);7519 vnode->hardlinks = getlist();7524 addnode (vnode->hardlinks, n);7868 if (vers->hardlinks)7871 walklist (vers->hardlinks, puthardlink_proc, fp);
2763 rev1_hardlinks = vp->hardlinks;2841 rev2_hardlinks = vp->hardlinks;
208 // sysctl may not return the desired path if there are multiple hardlinks
5124 $! easy to use DCL test to see if hardlinks are enabled on the build