>>>>> "Mad" == Mad Scientist <madscientist343_at_gmail.com> writes:
Mad> On Wed, Mar 12, 2008 at 6:23 AM, Andy Levy <andy.levy_at_gmail.com>
Mad> wrote:
>> On Wed, Mar 12, 2008 at 1:29 AM, Mad Scientist
>> <madscientist343_at_gmail.com> wrote: > Hi, I am looking to submit a
>> feature request for unversioned files > stored in the repository
>> along with normal versioned files. This could > be beneficial for
>> files such as project licenses which apply to all > revisions
>>
>> Why would these need to be unversioned but in the repository? Put
>> them in normally, and if they never change, how is it different
>> from keeping them in the repo, unversioned?
Mad> The benefit would be when the files do need to be changed and
Mad> applied to previous revisions ( eg a license that covers all
Mad> files in the repository ) you are able to change them on every
Mad> revision( from the view of a working copy ) instead of just
Mad> changing the latest revision.
You might be able to do this with externals.
Then again, it strikes me that what you're proposing is positively
evil -- something that goes directly against what any source control
system should do. The whole point of source control is to be able to
see history. The mechanism you describe specifically aims to destroy
history. This is bad. Subversion must not consider ever doing such a
thing.
paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-12 17:26:29 CET