On Mar 10, 2009, at 09:19, Bolstridge, Andrew wrote:
>> -----Original Message-----
>> From: Ryan Schmidt [mailto:subversion-2009a_at_ryandesign.com]
>> Sent: Tuesday, March 10, 2009 6:00 AM
>> To: Bolstridge, Andrew
>> Cc: users_at_subversion.tigris.org
>> Subject: Re: deleting files from the repository
>>
> ...
>>
>> While the dumpfile format is not complex, I'm sure it would take a
>> significant amount of work to write a tool that processes it
>> accurately. I would instead strongly recommend you look into the
>> existing tools that can modify dumpfiles, including svndumpfilter,
>> svndumptool, svndumpfilter2 and svndumpfilter3.
>>
> My problem is that I have roughly 100 files to remove, and my repo is
> very large - dumping it takes several hours and I was under the
> impression that svndumpfilter only excluded 1 (explicitly specified)
> file at a time.
> I'll have another go this weekend with svndumpfilter3.
My reading of the book is that you can exclude as many items as you
want.
http://svnbook.red-bean.com/en/1.5/
svn.ref.svndumpfilter.commands.c.exclude.html
>>> Wouldn't it be a good idea to set such a hook up by default for
>>> most repositories - it wouldn't be a newbie-knowledge problem, the
>>> first time someone checked in a banned file, they'd get a commit-
>>> error message telling them why and they could alter the hook.
>>
>> What criteria would you suggest the hook script use to reject files?
>> Are you talking about just matching certain filename extensions,
>> perhaps the same list Subversion uses by default for global-ignores?
>
> Yes, an alternative would be to block every file, the first thing an
> admin would do is delete or modify the list of extensions. If they
> forgot, they'd be reminded the first time they try to add a new file.
> The list could be extended dramatically - the current default set
> doesn't include many windows development exclusions, and will probably
> be always out of date, so exclude practically everything by default.
I don't think the devs will be keen on a modification that makes new
repositories non-functional by default.
It would probably be fine to include a new hook script in the contrib
directory showing how to do this kind of check. Then again, maybe the
enforcer script can already be used to do this.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1306267
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-11 05:25:42 CET