On Apr 26, 2007, at 16:37, Greg Cerveny wrote:
> 2007/4/26, Ryan Schmidt:
>
>> On Apr 26, 2007, at 13:39, Drew wrote:
>>
>> > I've got a couple of files in my project that get modified by users
>> > with no intention of commiting these changes to the repository. In
>> > particular, the project definition files I'm using contain
>> > checksums that use information about the modification time of the
>> > source files, so every user has a different version of this file.
>> > However, the file must still be revision controlled.
>> >
>> > Has anyone discussed having an 'ignore' feature for versioned
>> > files, so that these files would only be committed when explicitly
>> > selected to be committed, and not continually be flagged as
>> > 'modified'? I found a few threads asking about this, but haven't
>> > seen any productive discussion about it. Someone once suggested
>> > using a file 'template', but this seems like a clumsy workaround
>> > rather than a solution. I'd be willing to try my hand at
>> > developing such a feature if I knew it would be well-received by
>> > the subversion community. Does anyone have any strong feelings
>> > against such a feature?
>>
>> Your so-called "clumsy workaround" is the recommended solution to
>> this problem:
>>
>> http://subversion.tigris.org/faq.html#ignore-commit
>
> Ahh similar...
>
> That solution says check out a file template, have the user overwrite
> with changes, and give the folder the property to ignore it.
Well, that solution says check out a file template, have the user
copy it to the actual filename and then make changes as desired. It
also says that you can set a property on the folder so that the user
will not see the actual filename as needing to be added when looking
at the status output. Note that setting the property is a one-time
thing; it doesn't need to be done every time you check out.
> I was saying check the file out, have the user overwrite with changes,
> and global-ignore option in the client.
Yeah, Subversion doesn't have that feature though.
> Pretty much the same though...
>
> How about a precommit script?
All hook scripts run on the server, not on the client. You could
write a pre-commit script which would reject any attempt to commit to
the file. However, it would still be up to the user to remember not
to attempt to commit it. Also, what if you need to make legitimate
changes to the file?
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 26 23:56:24 2007