comments in line:
On 11 Aug 2006, at 17:13, Les Mikesell wrote:
> On Thu, 2006-08-10 at 19:43 -0400, Nico Kadel-Garcia wrote:
>
>>>> You could also require some review process before checkin.
>>>
>>> How? How can I see just the changes they'd like to make, and
>>> approve or
>>> disapprove of them?
>>
>> Take control of a "tags" or your "branches", by playing with
>> svnperms.py and
>> svnperms.conf. It easily allows one to set permissions to allow
>> the creation
>> of new tags, but their deletion only by a sitemaster, and changes
>> to trunk
>> only by the sitemaster. So force them to create a tag, then be
>> ready to
>> merge that tag when you're done.
>
> This doesn't really deal with the issue of getting cruft you don't
> want into the repository at all. If someone commits a bunch of
> huge files (or content that could incite a lawsuit for that matter)
> to a tag you can delete it so you don't see it in a HEAD view of
> the repository, but the content is still taking space in the
> repository and you can see it at the revision or time views when
> it was there.
I would tend to go for the "require a review process" idea. This
will have the advantage that it will educate your users about what
they should and shouldn't be checking in since that is the underlying
problem and anything else is just treating the symptoms..
>
> --
> Les Mikesell
> lesmikesell@gmail.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 14 12:08:12 2006