1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
moby--moby/vendor/github.com/Microsoft/go-winio
Sebastiaan van Stijn e5d28115ee
vendor: regenerate
- all changes here are attributed to difference in behaviour between,
  namely:
  - resolution of secondary test dependencies
  - prunning of non-Go files

Signed-off-by: Ilya Dmitrichenko <errordeveloper@gmail.com>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-01-18 15:46:04 +01:00
..
backuptar vendor: Update go-winio to v0.5.1 2021-10-15 14:33:34 -07:00
pkg vendor: regenerate 2022-01-18 15:46:04 +01:00
vhd vendor: Update go-winio to v0.5.1 2021-10-15 14:33:34 -07:00
.gitignore vendor: regenerate 2022-01-18 15:46:04 +01:00
backup.go
CODEOWNERS vendor: regenerate 2022-01-18 15:46:04 +01:00
ea.go
file.go
fileinfo.go vendor: Update go-winio to v0.5.1 2021-10-15 14:33:34 -07:00
hvsock.go Update Microsoft/go-winio to version 0.4.19 2021-04-26 10:02:58 -07:00
LICENSE
pipe.go
privilege.go Update Microsoft/go-winio to version 0.4.19 2021-04-26 10:02:58 -07:00
README.md vendor: Update go-winio to v0.5.1 2021-10-15 14:33:34 -07:00
reparse.go
sd.go
syscall.go Update Microsoft/go-winio to version 0.4.19 2021-04-26 10:02:58 -07:00
zsyscall_windows.go vendor: Update go-winio to v0.5.1 2021-10-15 14:33:34 -07:00

go-winio Build Status

This repository contains utilities for efficiently performing Win32 IO operations in Go. Currently, this is focused on accessing named pipes and other file handles, and for using named pipes as a net transport.

This code relies on IO completion ports to avoid blocking IO on system threads, allowing Go to reuse the thread to schedule another goroutine. This limits support to Windows Vista and newer operating systems. This is similar to the implementation of network sockets in Go's net package.

Please see the LICENSE file for licensing information.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

We also require that contributors sign their commits using git commit -s or git commit --signoff to certify they either authored the work themselves or otherwise have permission to use it in this project. Please see https://developercertificate.org/ for more info, as well as to make sure that you can attest to the rules listed. Our CI uses the DCO Github app to ensure that all commits in a given PR are signed-off.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Special Thanks

Thanks to natefinch for the inspiration for this library. See https://github.com/natefinch/npipe for another named pipe implementation.