$ nmi-extract-results --date <date> <RunID>
{endcode}
*:::: The --runid search modes aren't all that painful at all, it generally finds the matching RunID in well less than a minute, so it's much better than the "run find by hand" method, which is painful.
-*:::: If it succeeds in finding the build, it will then extract all of the relevant binaries into ./public/v7.1.2 (well, actually, the correct name). When it's done, you should have everything you need in that directory, including the condor_src and windows tarballs (note, however, that we, as of yet, still need to have Ben build the ZIP and MSI files).
-*:::: Copy the files back to one of the CSL machines; I try to use nation or one of the less used machines, especially if I'm copying directly into AFS, otherwise it loads them down badly (AFS just doesn't handle it well at all).
+*:::: If it succeeds in finding the build, it will then extract all of the relevant binaries into ./public/v7.1.2 (well, actually, the correct name). When it's done, you should have everything you need in that directory, including the condor_src and windows tarballs (note, however, that we, as of yet, still need to have Todd, Cathrin, or Z build the ZIP and MSI files).
+*:::: Copy the files back to one of the CSL machines; I try to use nation or one of the less used machines (nation is a good choice), especially if I'm copying directly into AFS, otherwise it loads them down badly (AFS just doesn't handle it well at all).
{code}
$ cd public/v7.1.4
$ rsync -av --rsh=ssh * nation:/p/condor/public/binaries/v7.1/7.1.4
