dev  

Messages by Thread

• • Re: multi-wc-format review Nathan Hartman
  • Re: multi-wc-format review Daniel Sahlberg
  • Re: multi-wc-format review Julian Foad
  • Re: multi-wc-format review Nathan Hartman
  • Re: multi-wc-format review Julian Foad
  • Re: multi-wc-format review Daniel Shahaf
  • Re: multi-wc-format review Daniel Shahaf
  • Re: multi-wc-format review Daniel Shahaf
• Re: svn commit: r1897443 - in /subversion/trunk/subversion/tests/cmdline/svntest: actions.py main.py Daniel Shahaf
  • Re: svn commit: r1897443 - in /subversion/trunk/subversion/tests/cmdline/svntest: actions.py main.py Jun Omae
  • Re: svn commit: r1897443 - in /subversion/trunk/subversion/tests/cmdline/svntest: actions.py main.py Daniel Shahaf
• Pristines-on-demand: authz denied during textbase sync Julian Foad
  • Re: Pristines-on-demand: authz denied during textbase sync Julian Foad
  • Re: Pristines-on-demand: authz denied during textbase sync Daniel Shahaf
  • Re: Pristines-on-demand: authz denied during textbase sync Daniel Shahaf
  • Re: Pristines-on-demand: authz denied during textbase sync Julian Foad
  • Re: Pristines-on-demand: authz denied during textbase sync Daniel Shahaf
  • Re: Pristines-on-demand: authz denied during textbase sync (#4888) Julian Foad
  • Re: Pristines-on-demand: authz denied during textbase sync (#4888) Julian Foad
  • Re: Pristines-on-demand: authz denied during textbase sync (#4888) Evgeny Kotkov
  • Re: Pristines-on-demand: authz denied during textbase sync (#4888) Julian Foad
  • Re: Pristines-on-demand: authz denied during textbase sync (#4888) Karl Fogel
  • Re: Pristines-on-demand: authz denied during textbase sync (#4888) Daniel Shahaf
  • Re: Pristines-on-demand: authz denied during textbase sync Daniel Shahaf
• Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Ivan Zhakov
  • Re: A two-part vision for Subversion and large binary objects. Johan Corveleyn
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Nathan Hartman
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Nathan Hartman
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Nathan Hartman
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Nathan Hartman
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Daniel Shahaf
  • Re: A two-part vision for Subversion and large binary objects. Daniel Sahlberg
  • Re: A two-part vision for Subversion and large binary objects. Daniel Shahaf
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Daniel Sahlberg
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Daniel Sahlberg
  • Re: A two-part vision for Subversion and large binary objects. Mark Phippard
  • Re: A two-part vision for Subversion and large binary objects. Vincent Lefevre
  • Re: A two-part vision for Subversion and large binary objects. Daniel Sahlberg
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Daniel Sahlberg
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Daniel Shahaf
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Daniel Shahaf
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Daniel Shahaf
  • Re: A two-part vision for Subversion and large binary objects. Daniel Shahaf
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Re: A two-part vision for Subversion and large binary objects. Julian Foad
  • Initial patch for storing the pristines-on-demand setting in the working copy (Issue 4889) Evgeny Kotkov
  • Re: Initial patch for storing the pristines-on-demand setting in the working copy (Issue 4889) Julian Foad
  • Re: Initial patch for storing the pristines-on-demand setting in the working copy (Issue 4889) Evgeny Kotkov via dev
  • Getting to first release of pristines-on-demand feature (#525). Karl Fogel
  • Re: Getting to first release of pristines-on-demand feature (#525). Nathan Hartman
  • Re: Getting to first release of pristines-on-demand feature (#525). Evgeny Kotkov via dev
  • Re: Getting to first release of pristines-on-demand feature (#525). Evgeny Kotkov via dev
  • Re: Getting to first release of pristines-on-demand feature (#525). Karl Fogel
  • Re: Getting to first release of pristines-on-demand feature (#525). Evgeny Kotkov via dev
  • Re: Getting to first release of pristines-on-demand feature (#525). Karl Fogel
  • Re: Getting to first release of pristines-on-demand feature (#525). Julian Foad
  • Re: Getting to first release of pristines-on-demand feature (#525). Nathan Hartman
  • Re: Getting to first release of pristines-on-demand feature (#525). Johan Corveleyn
  • Re: Getting to first release of pristines-on-demand feature (#525). Karl Fogel
  • Re: Getting to first release of pristines-on-demand feature (#525). Evgeny Kotkov via dev
  • Re: Getting to first release of pristines-on-demand feature (#525). Daniel Sahlberg
  • Re: Getting to first release of pristines-on-demand feature (#525). Karl Fogel
  • Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format (was: Re: Getting to first release of pristines-on-demand feature (#525).) Evgeny Kotkov via dev
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format (was: Re: Getting to first release of pristines-on-demand feature (#525).) Branko Čibej
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format (was: Re: Getting to first release of pristines-on-demand feature (#525).) Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Branko Čibej
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Sahlberg
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Branko Čibej
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Evgeny Kotkov via dev
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Evgeny Kotkov via dev
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Nathan Hartman
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Nathan Hartman
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Martin Edgar Furter Rathod
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Nathan Hartman
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Evgeny Kotkov via dev
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Glossary of attacks (was: Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format) Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Evgeny Kotkov via dev
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Evgeny Kotkov via dev
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Evgeny Kotkov via dev
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Evgeny Kotkov via dev
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Evgeny Kotkov via dev
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Karl Fogel
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Shahaf
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Johan Corveleyn
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Sahlberg
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Nathan Hartman
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Nathan Hartman
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Sahlberg
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Branko Čibej
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Evgeny Kotkov via dev
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Evgeny Kotkov via dev
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Daniel Sahlberg
  • Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format Nathan Hartman
  • Re: Getting to first release of pristines-on-demand feature (#525). Karl Fogel
  • Re: Getting to first release of pristines-on-demand feature (#525). Nathan Hartman
  • Re: Getting to first release of pristines-on-demand feature (#525). Daniel Shahaf
  • Re: Getting to first release of pristines-on-demand feature (#525). Evgeny Kotkov via dev
  • Re: Getting to first release of pristines-on-demand feature (#525). Karl Fogel
  • Re: Getting to first release of pristines-on-demand feature (#525). Evgeny Kotkov via dev
  • Re: A two-part vision for Subversion and large binary objects. Daniel Shahaf
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Linking to the archives (was: Re: A two-part vision for Subversion and large binary objects.) Daniel Shahaf
  • Re: A two-part vision for Subversion and large binary objects. Nathan Hartman
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
• Help with FAIL: wc-queries-test 3: test query expectations Julian Foad
  • Re: Help with FAIL: wc-queries-test 3: test query expectations Daniel Shahaf
  • Re: Help with FAIL: wc-queries-test 3: test query expectations Daniel Shahaf
  • Re: Help with FAIL: wc-queries-test 3: test query expectations Julian Foad
  • Double-checking 'pristines-on-demand-on-mwf' branch doc update. Karl Fogel
  • Re: Double-checking 'pristines-on-demand-on-mwf' branch doc update. Julian Foad
• svn copy --pin-externals pins relative paths to non existing revision/path Martin Obermeir
  • Re: svn copy --pin-externals pins relative paths to non existing revision/path Stefan Sperling
  • Re: svn copy --pin-externals pins relative paths to non existing revision/path Martin Obermeir
• Re: Make: missing dependency on config_keys.inc Daniel Shahaf
• Re: Make 'svn patch' keep permissions of patched files Karl Fogel
  • Re: Make 'svn patch' keep permissions of patched files Daniel Shahaf
  • Re: Make 'svn patch' keep permissions of patched files Ruediger Pluem
  • Re: Make 'svn patch' keep permissions of patched files Daniel Shahaf
  • Re: Make 'svn patch' keep permissions of patched files Ruediger Pluem
  • Re: Make 'svn patch' keep permissions of patched files Daniel Shahaf
• Re: [PATCH] Sketch of per-user/per-wc config for pristines-mode Julian Foad
  • Re: [PATCH] Sketch of per-user/per-wc config for pristines-mode Karl Fogel
  • Re: [PATCH] Sketch of per-user/per-wc config for pristines-mode (#4889) Julian Foad
  • Re: [PATCH] Sketch of per-user/per-wc config for pristines-mode Evgeny Kotkov
• Re: Multi-WC-format branch: preparing for merge to trunk Julian Foad
  • Re: Multi-WC-format branch: preparing for merge to trunk Mark Phippard
  • Re: Multi-WC-format branch: preparing for merge to trunk Julian Foad
  • Re: Multi-WC-format branch: preparing for merge to trunk Julian Foad
  • Re: Multi-WC-format branch: preparing for merge to trunk Julian Foad
  • Issue #4883: Multi-WC-format Julian Foad

• Later messages