"Daniel Becroft" <Daniel.Becroft_at_supercorp.com.au> writes:
> I have wondered about the absence of this feature for a while. However,
> my use case is somewhat simpler.
>
> I only ever require the revision of the working copy/export when
> exporting the codeset, rather than a checkout.
>
> We use exports to use as the basis for the builds, and in our version.*
> file, we include the revision that was used.
>
> Would it be possible to introduce certain keywords that are expanded
> only on export e.g $ExportRevisionID$? Probably not, but it's just a
> thought.
Hmm. I think that *would* be technically feasible, but are you
proposing that those keywords would only be expanded on export and not
on regular checkout? I'm not sure it's wise to introduce that kind of
difference in the file contents produced by the two operations (export
is supposed to produce exactly what checkout would!), especially not
when there are pretty easy workarounds (just remember the revision you
exported and run your own substitution script).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-02 17:11:20 CEST