Skip to content

docs: remove stale 100-subdirectories sync-depth FAQ (7.1)#743

Open
DeepDiver1975 wants to merge 1 commit into
7.1from
fix/728-100-subdir-faq-7.1
Open

docs: remove stale 100-subdirectories sync-depth FAQ (7.1)#743
DeepDiver1975 wants to merge 1 commit into
7.1from
fix/728-100-subdir-faq-7.1

Conversation

@DeepDiver1975

Copy link
Copy Markdown
Member

What

Removes the FAQ section "Sync Stops When Trying to Sync Deeper Than 100 Subdirectories" from faq.adoc.

Why

The claimed hard limit of 100 subdirectories is stale for 7.1. Verified against the owncloud/client v7.1.0 source:

  • CSYNC_STATUS_INDIVIDUAL_TOO_DEEP (src/csync/csync.h:85) is declared but never set anywhere in src/.
  • There is no MAX_DEPTH constant in the codebase.

The depth limit no longer exists, so the FAQ entry is removed rather than corrected.

Refs #728 (master PR carries the closing keyword).

🤖 Generated with Claude Code

The FAQ claimed the Desktop App is hard-limited to sync no deeper than
100 subdirectories. This is no longer accurate for 7.1. In the
owncloud/client v7.1.0 source, the CSYNC_STATUS_INDIVIDUAL_TOO_DEEP
enum (src/csync/csync.h) is declared but never set anywhere, and no
MAX_DEPTH constant exists. The depth limit was removed, so drop the
stale FAQ section.

Closes #728

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>

@DeepDiver1975 DeepDiver1975 left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated code review by Claude Code review agent

Approve. 7.1 port removing the stale 100-subdirectories sync-depth FAQ section from faq.adoc.

  • Removed content verified obsolete (no depth limit / MAX_DEPTH in client v7.1.0; CSYNC_STATUS_INDIVIDUAL_TOO_DEEP declared but unused). Surrounding sections remain intact, no dangling references.
  • AsciiDoc syntax correct.

Pair consistency: byte-identical change to master PR #744, correctly targets the 7.1 branch, uses Refs #728 (closing keyword on master PR). LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant