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

Force commit of unchanged file

From: Phil Cairns <phil.cairns_at_gmail.com>
Date: 2006-06-20 06:14:59 CEST


I'm developing using VC2003, and I used to use a program that would
parse my resource file and increment the last value in my version
resource during a release build. This is kind of a nuisance, since
updating the resource file means that the project is going to rebuild,
which means that the version number is going to increment, and on it
goes. Sort of. Because sometimes it builds fast enough, and the file
system timestamps aren't high-res.

So, what I've done is include a string resource that looks like this:

     IDS_SVNREVISION "$Rev: 1948 $"

At least, that's what it is now that the file has been committed. This
particular file has the svn:keywords="Rev" property set, so that
whenever I update and then commit this file, it will have this string
resource updated.

That's good as far as it goes, but what I'd really like is for this file
to be updated and committed whenever I do a commit in this directory,
regardless of whether or not this particular file has changed. Failing
that, be able to right-click and commit without having TortoiseSVN tell
me that "there is is nothing for TortoiseSVN to do here..."

Is such a thing possible with TortoiseSVN? Is there an "always allow
commit" property?


To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Jun 20 06:20:22 2006

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

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