Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update README.md #2940

Merged
merged 1 commit into from
Feb 4, 2024
Merged

docs: update README.md #2940

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,7 @@ And it adds several innovative, useful features of its own:
repositories to S3? No? Well, now you can!

The fundamental problem with using filesystems like Dropbox and backup tools
like `rsync` on your typical Git/Mercurial repositories is that that they rely
like `rsync` on your typical Git/Mercurial repositories is that they rely
on *local filesystem operations* being atomic, serialized, and non-concurrent
with respect to other reads and writes—which is _not_ true when operating on
distributed file systems, or when operations like concurrent file copies (for
Expand Down