Hi all,
Our mergeinfo on /trunk as grown to almost 100 branch
entries now. Most of those branches don't exist anymore.
Although we technically could, we will neither merge from
them (using the branch@rev notation) nor resurrect them
in the future. Therefore, I'd like to shave off 15k from our
mergeinfo by removing those unused entries. List below.
Is there a compelling reason not to do it?
-- Stefan^2.
1.10-cache-improvements
1.5.x-r30215
1.7.x-fs-verify
10Gb
atomic-revprop
auto-props-sdc
bdb-reverse-deltas
cache-server
diff-callbacks3
diff-optimizations
diff-optimizations-bytes
dont-save-plaintext-passwords-by-default
double-delete
dump-load-cross-check
explore-wc
file-externals
fs-rep-sharing
fsfs-format7
fsfs-improvements
fsfs-lock-many
fsfs-pack
fsx
fsx-1.10
fsx-id
gnome-keyring
gpg-agent-password-store
gtest_addition
http-protocol-v2
in-memory-cache
in-repo-authz
inheritable-props
integrate-cache-item-serialization
integrate-cache-membuffer
integrate-compression-level
integrate-io-improvements
integrate-is-cachable
integrate-partial-getter
integrate-readline-speedup
integrate-stream-api-extensions
integrate-string-improvements
integrate-txdelta-caching
issue-2779-dev
issue-2843-dev
issue-3000
issue-3067-deleted-subtrees
issue-3148-dev
issue-3220-dev
issue-3242-dev
issue-3334-dirs
issue-3975
issue-4194-dev
kwallet
log-g-performance
merge-skips-obstructions
multi-layer-moves
nfc-nfd-aware-client
node_pool
performance
pin-externals
py-tests-as-modules
ra-svn-tuning
ra_serf-digest-authn
reintegrate-improvements
remote-only-status
revprop-cache
subtree-mergeinfo
svn-auth-x509
svn-info-detail
svn-mergeinfo-enhancements
svn-mergeinfo-normalizer
svn-patch-improvements
svn_mutex
svnpatch-diff
svnraisetc
svnserve-logging
tc-issue-3334
tc-merge-notify
tc-resolve
tc_url_rev
tree-conflicts
tree-conflicts-notify
tristate-chunked-request
tweak-build-take-two
uris-as-urls
verify-at-commit
verify-keep-going
wc-collate-path
