RFC should core.fsyncObjectFiles fsync the dir entry + docs
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 20 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | sha1-file: fsync() loose dir entry when core.fsyncObjectFilessha1-file.c | +14 | 12 replies | |
| 2/2 | core.fsyncObjectFiles: make the docs less flippantDocumentation/ | +36 | 8 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Christoph Hellwig |
|---|---|
| 1/2 | A-b |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [RFC PATCH 0/2] should core.fsyncObjectFiles fsync the dir entry + docs
I was re-reading the
https://lore.kernel.org/git/[email protected]/ thread today and thought we should at least update the docs, and per my earlier E-Mail in
https://lore.kernel.org/git/[email protected]/
perhaps the directory entry should also be synced.
I kept [email protected] in the CC, it was in the original thread, but more importantly it would be really nice to have people who know more about the state of filesystems on Linux and other OS's to give 2/2 a read to see how accurate what I put together is.
Ævar Arnfjörð Bjarmason (2):
sha1-file: fsync() loose dir entry when core.fsyncObjectFiles core.fsyncObjectFiles: make the docs less flippant
Documentation/config/core.txt | 42 ++++++++++++++++++++++++++++++----- sha1-file.c | 19 +++++++++++----- 2 files changed, 50 insertions(+), 11 deletions(-)
Signature · 1 line
2.28.0.297.g1956fa8f8d