Checkout Tools
  • last updated 6 hours ago
Constraints: committers
Constraints: files
Constraints: dates

Changeset 1866189 is being indexed.

* tools/dist/ Revert accidental change made in r1866188.
Issue #4828, Hide experimental commands and options by default.

* subversion/libsvn_subr/opt.c


print_generic_help_body3): Show commands and options starting with

'x-' only if new 'with_experimental' option is true.

(print_generic_help): Extracted from 'svn_opt_print_generic_help3', to

take the new 'with_experimental' option.

(subcommand_help): Extracted from 'svn_opt_subcommand_help4', to

take the new 'with_experimental' option.

(svn_opt_print_help5): Let the 'verbose' option control 'with

experimental', when printing help. The 'verbose' option previously was

not used here except for the case of printing version info.

* subversion/svn/svn.c

Let 'help' take the '-v' option.

* subversion/tests/cmdline/getopt_tests_data/svn_help_stdout

* subversion/tests/cmdline/getopt_tests_data/svn--help_stdout

Adjust the expected output.

* tools/dist/

[Accidental change; reverted in 1866189.]

* docs/community-guide/releasing.part.html

(#release-stabilization-how-many-votes): Simplify.

* docs/community-guide/releasing.part.html

(#release-stabilization): Fix broken link.

* docs/community-guide/releasing.part.html: Use markup.
* docs/community-guide/releasing.part.html

(#release-stabilization): Mention and interactive mode.

* docs/community-guide/releasing.part.html

(#release-stabilization): Remove a paragraph.

"Vote if consensus fails" is the default; it needn't be spelled out.

* docs/community-guide/releasing.part.html

(#release-stabilization): Reorganization.

Add subsection headers.

Move paragraphs for flow.

Add some content (no new policies, of course).

Remove the "(for 1.7.2)" example. We don't need to spell out the

possibility of doing that.

Sync-merge from publish
    • ?
    • ?
  1. … 4 more files in changeset.
* CHANGES: Fill in changes for upcoming release 1.13.0.
Publish some info on how we handle security issues.

Moved from:

* publish/docs/community-guide/issues.part.html

(#security): Point to information. Add sub-headings.

* publish/docs/community-guide/how-to-roll-releases-in-private.txt

New, extracted from the README.

* STATUS: Declare 1.11.x as 'CLOSED'.
* STATUS: Cast some votes.
* STATUS: Cast some votes.
* STATUS: Cast some votes.
* subversion/svnserve/serve.c

(construct_server_baton): Report some errors that we previously ignored.

* notes/commit-access-templates/full-committer.tmpl:

Almost revert r1866031, leaving just the http:// -> https:// change.

Update URLs in the commit access invitation templates.
* subversion/libsvn_fs_fs/verify.c (compare_p2l_to_rev):

Fix format string that was broken on 32-bit platforms.

Follow-up to r1865929: Change test to XFail, adding issue number.
Follow-up to r1865929: Restore Windows compatibility in test.
Add a test for issue #4826, diff repos-wc non-infinite depth uses wrong depth.
Fix issue #4822, "svn diff --changelist ARG" broken in subdirectories.

A follow-up to r1835234.

* subversion/libsvn_wc/diff_local.c

(svn_wc__diff7): Pass the correct anchor dir to the changelist filter.

* subversion/tests/cmdline/

(diff_with_changelists_subdir): New test.

(test_list): Run it.

Clarify LTS versus regular releases.

Suggested by: Thomas Singer <thomas.singer{_AT_}>

* download.html

Add a notice of latest LTS release after notice of latest regular release.

(#recommended-release): Change the title to "Latest regular release".

State the support period.

(#supported-releases): Change the title to "LTS releases".

State the support period.

Say "1.10 LTS" instead of just "1.10", and for 1.9, everywhere.

* index.html, news.html: remove incorrect anchors in links to download page in recent news items. Better with no anchor at all.
* site-nav.html (site-nav-menu): Remove currently unnecessary '?update=...' parameter from download link.
When compiling SQLite, enable the SQLITE_OMIT_WAL compile-time option.

We don't use WAL (write-ahead logging) feature of SQLite, but just keeping it

enabled has a visible I/O performance penalty, because SQLite has to check if

the write-ahead log file is present on disk. In a couple of my experiments,

disabling this feature resulted in a ~10% faster `svn st` on a large working


* subversion/libsvn_subr/sqlite3wrapper.c


When compiling SQLite, set the SQLITE_DEFAULT_MEMSTATUS=0 compile-time option.

This is the recommended option that is not enabled by default. Setting it to

zero avoids using a mutex (and thus suffering a performance penalty) during

every sqlite3_malloc() call, where this mutex is used to properly update the

allocations stats. We don't use sqlite3_status(), so set this option to zero.


* subversion/libsvn_subr/sqlite3wrapper.c


Win32: fix an incorrect error status being propagated to the caller in case

where we fail to stat the destination path while being in the middle of a

failed rename.

So, if we fail to stat the destination in the middle of such rename, propagate

the *original* error. Because overriding the original error with the new one

loses information about the actual cause of failure and may even confuse some

of the callers, who for instance attempt to recover in case of an EACCES,

since they may not be receiving that error at all.

(This is the behavior we had for a long time, even before r1865518, but now

seems to be an appropriate moment to fix that)

* subversion/libsvn_subr/io.c

(win32_file_rename): Use a separate `stat_err` for the case of the failed

GetFileAttributes() call. If we failed to stat the file, return the

original `err` status to the caller.

* subversion/libsvn_subr/io.c

(win32_file_rename): Rename `status` to `err`. This lays the groundwork for

fixing the incorrect error status being propagated to the caller in case

where we fail to stat the destination path while being in the middle of

a failed rename.