On Apr 4, 2012 3:26 PM, "Ashod Nakashian" <ashodnakash...@yahoo.com> wrote: > > > > > >________________________________ > > From: Daniel Shahaf <danie...@elego.de> >.... > >> > > > >But one _could_ write a filesystem that implements compression and/or > >deduplication aimed at .svn/pristine/'s workflow. Should effort be > >spent there rather than on implementing a smarter svn_wc__pristine_*()? > > Perhaps we should, but is that a simpler/easier/more-maintainable/first-try approach that we can defend with a straight face? I'm having a hard time doing that in my current mode. > > > > >Daniel > >(devil's advocate mode)
Given Daniel's devil's advocate position, I say just ignore him. Don't feed him :-) My vote is compress for files > N bytes (and store on disk), and stick the others into a new pristine.db. Maybe compress before inserting into Sqlite. Not sure. Add a few heuristics for skipping compression on certain files types. Shouldn't be too bad to start with that. Cheers, -g
