[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: File under versioncontrol with individual changes per developer

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-07-18 15:52:37 CEST

On Sun, 2004-07-18 at 08:40, Daniel Albuschat wrote:
> Ben Collins-Sussman wrote:
> > On Fri, 2004-07-16 at 08:51, Fran├žois Beausoleil wrote:
> >
> >>I can only offer a workaround...
> >
> > This is a common FAQ, so I just added it to our FAQ:
> >
> > http://subversion.tigris.org/project_faq.html#ignore-commit
> Thanks for the answers. I guess this will work.
> Perhaps there might be a `built-in' solution in an upcoming
> subversion release, though? There actually *are* ways how to
> handle this properly I guess.

Using templates as part of the build system is the most common thing in
the world. Heck, check out a copy of subversion itself and notice that
even 'configure.in' is under version control, but 'configure' is not.
Count how many "*.in" files are versioned and are converted to
unversioned files by the build system.

So no, I don't think there's any planned feature to teach 'svn commit'
to ignore versioned files.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jul 18 15:53:55 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.