Re: followup question to FAQ

"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.

> Are there any ways to customize the update, checkout, and export
> actions?

Well, you have access to the same source code we do, but .... :-)

"No," is probably the realistic answer, though.

> Is there some other way to do what I'd like to do that I've
> completely overlooked?

That depends on what you want to do, really.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 22 22:00:40 2004