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

Re: followup question to FAQ

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-10-25 16:57:15 CEST

"C. Michael Pilato" <cmpilato@collab.net> writes:

> "Entner, Jonathan T." <Jonathan.Entner@jhuapl.edu> writes:
>
> > Is there a way to force a commit of a particular file for every
> > commit transaction?
>
> DISCLAIMER: THE FOLLOWING HAS NOT BEEN ATTEMPTED. I'M NOT RESPONSIBLE
> FOR ANY NEGATIVE RESULTS THAT OCCUR FROM IT BEING ATTEMPTED.
> UNDERSTAND THAT SUBVERSION BEHAVIOR MAY CHANGE SUCH THAT THIS NO
> LONGER WORKS, IN WHICH CASE -- TOUGH LUCK, BUCK-O.
>
> So, the problem with modifying files in the pre-commit phase is the
> danger of the working copy claiming to have something that it does
> not. I wonder, though, if you could write a pre-commit hook that
> "touches" a particular file in such a way that a new revision of that
> file would be generated, but that the working copy wouldn't really
> care. For example, your script could set some property on the file
> that it doesn't already have, and then immediately remove that
> property, and then allow the commit to proceed. I think that would
> sufficiently fool the Subversion filesystem into generating a new
> revision of that file without completely horking your working copy.

So, I actually gave this idea a shot, and to my surprise, it doesn't
work. But it doesn't work for non-obvious reasons. I might have
uncovered a bug here. Watch this space for more.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 25 17:05:18 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.