In times past, I've wondered if the server couldn't just store line-delta information -- as a comparison between each FS DAG node and its immediate predecessor -- similar to the way that CVS does (and in addition to the stuff it already stores, of course). The line-delta info could be populated post-commit just as the BDB backend did deltafication, or perhaps also on demand (to rebuild this information for older servers) via some 'svnadmin' command. But it shouldn't ever change once calculated, right?
My only concern is in dealing with the definition of a "line". The FS layer today is happily file-content agnostic. All EOL translation stuffs are considered voodoo of interest only to the client layers. We could, of course, choose to make the FS layer pay attention to the likes of the svn:eol-style property, but that feels mucho icky. Thoughts? -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
