kfogel@collab.net wrote:
> Jamie Heilman <jamie@audible.transient.net> writes:
> > Currently there seems to be no way to do an export from a svn repo and
> > have it automatically expand keywords such that an import of the code
> > at another site will not lose previous keyword information.
> > Eg. keyword "$Id: foo 127 2004-05-26 19:41:28Z jamie $" would be
> > exported as "foo 127 2004-05-26 19:41:28Z jamie"
>
> Workaround: you could use the long forms of the keywords, which I
> believe CVS does not know about, and therefore would not expand.
I'm not sure how you came to the conclusion I was re-importing the
exported tree using CVS--you happen to be correct, but it didn't have
to be CVS, it could have been anything where there are keyword naming
"conflicts." As it happens the trees I usually do exports of aren't
in my control so I can't choose which keywords to use. I export them
so I can re-import on a vendor branch and keep track of upstream
changes in comparison to my fork. If I were using svn or anything
else, I'd still want to be able to export the trees and preserve the
upstream keywords while using my own though. Even if the keyword
syntax happened to collide between the version control software.
--
Jamie Heilman http://audible.transient.net/~jamie/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 8 05:23:06 2004