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

Re: [BUG] Conflict with use-commit-times = yes + svn:keywords set

From: Brian W. Fitzpatrick <fitz_at_collab.net>
Date: 2004-11-02 20:01:51 CET

On Nov 2, 2004, at 12:43 PM, John Peacock wrote:

> Brian W. Fitzpatrick wrote:
>> Unfortunately, since CVS stores the keywords expanded, and they do
>> contain data that could be important to people, I don't think that
>> this is an option.
> For the specific keywords that CVS and Subversion share in common, the
> contents of the keyword should be extracted from the CVS file and
> stored in the matching keyword prop field (and the keyword unexpanded
> in the file).

I think I understand the concept you're promoting here: Store the
expanded keyword value in a prop instead of in the expanded keyword
inside the contents of the file.

However, I'm not sure what you mean by "stored in the matching keyword
prop". Do you mean that we create a prop like "cvs:revision" and set
it to the appropriate value? This is doable, but we should make it a
revprop, and we could probably get away with just the CVS revision

> For all other keywords (here I am specifically thinking of $Log$),
> Subversion doesn't support them and the contents can be left
> "expanded" in the repository.

Hmm. Is there a way to get something out of CVS with only that one
keyword expanded?

> Is there some keyword you were thinking of that doing the above would
> lose information?



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 2 20:02:12 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.