On Wed, Aug 24, 2011 at 11:08 AM, Mark Phippard <markp...@gmail.com> wrote:
> On Wed, Aug 24, 2011 at 9:32 AM, Neels J Hofmeyr <ne...@elego.de> wrote: > >> We'd have to change the changelists feature, beyond recognition. >> Instead of adding a quick propget in basically one or two places, >> we do what, overhaul changelists + plaster it with special conditions. >> > > Why exactly? It seems we can declare anything on a certain named > changelist will be ignored from commit. All we have to do is change the > commit code to do this ignoring. IOW, we could just recreate the > TortoiseSVN feature and nothing more. I do not see where this changes the > changelist code. > > But ok, we can do that. Still, the question remains: what about Johan & >> Co., >> that only have a use for ignore-on-commit if it is *centrally >> configurable*. >> > > I do not think we HAVE to do this feature. It would be nice, but it seems > to raise some challenging problems that make it less nice. Personally, I > just think we should not do anything, including the changelists, and leave > the recommendation of using a template. > BTW, admins can also lock files in the repository to prevent accidental commits of sensitive information. -- Thanks Mark Phippard http://markphip.blogspot.com/
