Distinguish special inode kinds from absence #92
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-ipc!92
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/explicit-special-inode-kinds"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Represent original special inode kinds explicitly across metadata, directory and acquisition observations. Keep an unavailable object distinct from a FIFO, socket or device description without granting access to the represented object.
Depends on #91.
WIP: Distinguish special inode kinds from absenceto Distinguish special inode kinds from absencePrepared the merge history at 1689ded8 to remove duplicate upstream patches and integrate the feature on its prepared prerequisite history. The feature tree is unchanged.
Special inode kinds are now on the current directory-reply history. FIFO, character device, block device and socket metadata remain distinct from absence. Recognizing a kind does not create a pipe, device route or socket endpoint.
The signed current-parent preview is
0c666ffc955db3c9650976685946370607deb5f0. The original feature branch is preserved. This rewritten history needs its own review.