- Mention the addition of --itemize-changes.

- Mention the setting of read_only when a daemon is read-only.
This commit is contained in:
Wayne Davison
2005-02-15 19:47:57 +00:00
parent b78296cb0b
commit 5b4e1f318d

8
NEWS
View File

@@ -167,6 +167,10 @@ Changes since 2.6.3:
they are given, and refuse to operate on a directory index (since
that would indicate that something had gone very wrong).
- Added the --itemize-changes (-i) option that is a way to output the
list of files that got transferred and/or changed in any way, and how
they changed. Also works with --dry-run.
- Added the --fuzzy option, which attempts to find a basis file for a
file that is being created from scratch. The current algorithm
only looks in the destination directory for the created file, but
@@ -217,6 +221,10 @@ Changes since 2.6.3:
- Defined int32 in a way that ensures that the build dies if we can't
find a variable with at least 32 bits.
- The daemon's "read only" config item now sets an internal read_only
variable that makes extra sure that no write/delete calls on the
read-only side can succeed.
PROTOCOL DIFFERENCES FOR VERSION 29:
- If --inplace is specified, the generator sends an extra byte after