Re: Overwrite a file without history

This generates the same return question. Why do you want it in
Subversion if it's not a versioned resource (since that's what
Subversion does).

Store it in another location with similar accessibility but without
the imposition of revision retention.

Subversion doesn't offer any way, at all, not a bit, not even a
little, to have some files versioned and others not. Any commit
creates a new revision, that revision is retained (unless some dumping
and reloading is done with a little filtering in-between).

Can your build process or packaging process (or whatever depends on
the image) go and fetch the latest image from another form of storage?

--
Talden
On 12/4/06, Jordi Amatller <jamatller@tmira.com> wrote:
>
>
>
>
> Dear svn users,
>
>
>
> I have a question about commiting a file in the repository. I have a process
> that automatically generates an image every minute. The image file has
> always the same name and the same path. I want to commit the new image file
> generated into subversion repository every time, but I don't want to keep
> the history of the file, because the svn database size will grow very
> quickly. Is there a way to commit the changes in svn without making a new
> version of a file just overwriting the content?
>
>
>
> Thanks!
>
> Jordi
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org