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

Re: Let svn commit ingore files

From: John Peacock <john.peacock_at_havurah-software.org>
Date: Thu, 03 Apr 2008 10:47:44 -0400

Christoph Bartoschek wrote:
> We have no control over the build tool. Additonally my use case does not
> involve template files. I've changed files and links of the official project
> to be able to compile it on my notebook. This changes should not be commited
> to because they would break everything for other users.

It sounds like you want to have a private branch for your local changes
that would interfere with the upstream users. You may want to consider
installing SVK, which works particularly well in this respect
(especially with a disconnected notebook). You still need to take some
care when merging back to the mirrored repo, so that only the
appropriate changes get committed back.

One nice thing about SVK is that when you are writing a commit message,
you can delete files from "below the line" and SVK actually pays
attention and doesn't commit those files. Thus you could keep those
changed files uncommitted in your local WC indefinitely (as long as you
remembered to ignore them each time).


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-03 16:48:10 CEST

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