search for: go_

...OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: jidanni at jidanni.org QA Contact: rsync-qa at samba.org User very much wants to know where the files _will go_ before daring to try an actual run. He tries even rsync -vv --dry-run --itemize-changes -avz x.y.z:dir1/dir2/backup/ backup/ but still there is no way to make it say File x.y.z:dir1/dir2/backup/F1 will be copied to backup/F1 File x.y.z:dir1/dir2/backup/F2 will be copied to backup/F2 -- You are...

This feature is roughly finished now, although it needs a few more tests and some examples. It's pretty much up to par with all the other bindings, but it lacks a completely safe AIO buffer. It won't stop you from freeing the buffer too early) because golang's GC inexplicably lacks a way to declare a root from C. I can probably do it with a global variable and ref counting on the

Now runs a complete set of tests, notably including the AIO test. File descriptors are passed in and out as plain ints (instead of *os.File) for a couple of reasons: (1) We have to pass the plain int to syscall.Select. (2) Turning an fd into an os.File causes golang to set the blocking flag which is deeply unhelpful. Rich.