Re: Commiting file which contains the next revision number

Max Bowsher wrote:
> Nope, no good.
> The extra complication doesn't work round the essential problem:
> *ALL* file data must be written *before* the new revision number is known.

Yes, but my solution meets this requirement. To make it clearer what
happens:

In <file.txt> I use the tag: $Unique:LastRev$

When I do commit, this happens:
        1. Unique is found and a uniqe file is created, a UUID or something
that subersion guarantees is uniqe, for our exmplae choose "ABCD.FILE".
        2. The Unique reference is replaced with a named reference:
$Unique:LastRev$ => $ABCD.FILE:LastRev$
        3. Now the files can be written, then a revision number of known

Okay,but since the ABCD.FILE is unique, and is read-only (never changes)
the $ABCD.FILE:LastRev$ will always be the revision with which is was
first checked in, therefore, in <file.txt> the reference will always
contain the same revision number, and it will be the revision number
with which <file.txt> was checked in with.

Note: Some work on naming/display would of course be needed.

-- 
edA-qa mort-ora-y
Idea Architect
http://disemia.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org