dev  

Messages by Thread

• • 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
  • 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. Karl Fogel
  • Re: A two-part vision for Subversion and large binary objects. Karl Fogel
  • Sharing .svn directories across wc's (was: Re: A two-part vision for Subversion and large binary objects.) Daniel Shahaf
  • Re: Sharing .svn directories across wc's (was: Re: A two-part vision for Subversion and large binary objects.) Daniel Sahlberg
  • Re: Sharing .svn directories across wc's (was: Re: A two-part vision for Subversion and large binary objects.) Daniel Shahaf
  • Re: Sharing .svn directories across wc's (was: Re: A two-part vision for Subversion and large binary objects.) Branko Čibej
  • 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. 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. Nathan Hartman
  • 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. Daniel Shahaf
• Re: Jira issues cleanup Johan Corveleyn
  • Re: Jira issues cleanup Daniel Sahlberg
  • Re: Jira issues cleanup Nathan Hartman
• Re: svn commit: r1896877 - /subversion/trunk/subversion/svnadmin/svnadmin.c Nathan Hartman
  • Re: svn commit: r1896877 - /subversion/trunk/subversion/svnadmin/svnadmin.c Stefan Sperling
• Re: svn commit: r1896898 - /subversion/branches/1.14.x/STATUS Daniel Sahlberg
  • Re: svn commit: r1896898 - /subversion/branches/1.14.x/STATUS Nathan Hartman
• Re: Subversion reports status fault on substituted drive Nathan Hartman
• Re: svn commit: r1896485 - /subversion/site/staging/download.html Nathan Hartman
  • Re: svn commit: r1896485 - /subversion/site/staging/download.html Nathan Hartman
• Re: svn commit: r1896611 - /subversion/site/staging/mailing-lists.html Nathan Hartman
• New release Daniel Sahlberg
  • Re: New release Nathan Hartman
  • Re: New release Johan Corveleyn
  • Re: New release Julian Foad
  • Re: New release Daniel Sahlberg
  • Re: New release Johan Corveleyn
  • Re: New release Daniel Sahlberg
  • New release Daniel Sahlberg
  • Re: New release Stefan Sperling
  • Re: New release Johan Corveleyn
  • Re: New release Nathan Hartman
  • Re: New release Daniel Sahlberg
  • Re: New release Nathan Hartman
  • Re: New release Stefan Sperling
  • Re: New release Daniel Sahlberg
  • Re: New release Mark Phippard
  • Re: New release Nathan Hartman
  • Re: New release Johan Corveleyn
  • Re: New release Nathan Hartman
  • Re: New release Daniel Sahlberg
  • Re: New release Nathan Hartman
  • Re: New release Daniel Sahlberg
  • Re: New release Nathan Hartman
  • Re: New release Daniel Sahlberg

• Later messages