Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
This builds and tests everything with all the TLS patches in. I assume we now wait for these patches to be accepted upstream and update to the release archives as they happen?
Things needing to be merged/released:
once mirage mirage/mirage#394 PR is merged, and there are some releases (nocrypto, tls, mirage-entropy-xen), we'll need gmp-xen and zarith-xen; which might both be sensible to drag in via a
this PR in tls is intentionally not merged, to not introduce a dependency on
When the Vfs code got split out from the 9p support, the unique inode ID wasn't included. Instead, the 9p support started minting a new ID each time it was asked for one. This meant that clients saw a new inode number each time they asked for it. This confused cp at least, which checks that the inode number is the same before and after opening the file. Fixes mirage#52. Signed-off-by: Thomas Leonard <firstname.lastname@example.org>