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?
> or the latest generated files for people who do not want or
> are unable to compile/build the files themselves.
Have your build manager put them into a "release" tag which no one
else is allowed to commit to, or place the items on a fileserver.
> It keeps could also
> keep the generated files in an easy to remove format when they become
> out dated or space becomes an issue.
This would require a very large change to Subversion - basically,
you're asking for "svn obliterate" here, which I think is under
consideration but involves a very large amount of work.
> I was thinking maybe these files
> could be stored internally ( just a guess/suggestion ) at revision 0 or
> -1 and override any versioned files.( could allow misplaced files to be
> 'removed' as a quick patch until the repository is fixed, confidential
> data on a public repository for instance )
This sounds like it could get real messy and provide the potential for
work to be lost.
---------------------------------------------------------------------
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 12:24:06 CET