Re: proposed export option

Hello, I previously inquired about adding a –skipfilesmatchingsize option to the export subcommand. I have implemented that feature, and I was wondering if it has any chance of making it into the trunk directory for svn. It currently has performance issues, and I don't want to spend a lot of time optimizing the code if it's never going to be incorporated into the main development line. If the feature is not acceptable as described in my previous message, could it be made acceptable if it were expanded somehow to make it of more general use? Maybe by using checksums instead of file size or, more ambitiously, I was thinking something like a rsync subcommand that allows a person to synchronize an unversioned folder with an svn repository. Any comments or suggestions would be greatly appreciated. --Paul Breen --- On Mon, 4/26/10, Paul Breen <greenbreen_at_yahoo.com> wrote: > From: Paul Breen <greenbreen_at_yahoo.com> > Subject: proposed export option > To: users_at_subversion.apache.org > Date: Monday, April 26, 2010, 11:07 PM > Hello, > > I'd like to add a new option to the export command that > allows the user > to export files only if the file size has > changed--something like > > svn export --skipfilesmatchingsize > > The idea is to do a quick-and-easy, traffic-minimizing > deployment of > files that are unlikely to remain the same size when > modified.  I'm > doing this as a project for a client who would like the > change to be > incorporated into a release version on Collabnet's > website.  I'm new > to subversion development, and I'm looking for any advice > or > suggestions the developers here may have regarding the > proposition. > > Thanks, > > Paul Breen >
Received on 2010-06-02 20:48:47 CEST