Rainer M Krug wrote: > True - but the alternative is to code the tests, which is, as discussed, > quite problematic.
or to steal them from git. > There is this option for git status which could be used: > --porcelain > Give the output in a stable, easy-to-parse format for scripts. > Currently this is identical to --short output, but is guaranteed > not to change in the future, making it safe for scripts. good to know, thanks. > > 3. possible network problems written in other mail. > > > > But if "git status" does not work, I do not expect the other "git" commands > to work? the problem i'm pointing to is that user who doesn't work with any RCS system may experience freezes when loading file just because we are playing in unrelated parts of the file system. pavel
