Searched full:changes (Results 1 – 6 of 6) sorted by relevance
351 CHANGES=$(git log --oneline $PREV.. --grep='^Merge' --invert-grep)352 printf "CHANGES\n%s\n\n" "$CHANGES"367 \"body\": $(jq -sR '.' <<< "$CHANGES")
22 // Major (top-nibble), incremented on backwards incompatible changes29 // Major (top-nibble), incremented on backwards incompatible changes
63 bounded. This means RAM usage does not grow as the filesystem changes in113 changes, while reading requires traversing the log to reconstruct a file.187 a copy with the changes and replacing any references to the old block with217 storing data changes directly in a log. They even disassociate the storage419 write all of these changes to the second block without worrying about power566 elements are immutable. Making changes to the data requires creating new1877 know and xor it with both our changes and any existing delta in the metadata1878 pair. Committing this new delta to the metadata pair commits the changes to
1739 // calculate changes to the directory in lfs_dir_commit()2415 // get id, add to list of mdirs to catch update changes in lfs_file_opencfg()4257 // Major (top-nibble), incremented on backwards incompatible changes4264 // Major (top-nibble), incremented on backwards incompatible changes
697 operation that changes metadata pairs on the threaded linked-list.
209 // sync to make sure we persist the last changes in lfs_testbd_prog()256 // sync to make sure we persist the last changes in lfs_testbd_erase()
