Keyword expansion causes merge conflict

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Thomas Linder Puls
Posts: 153
Joined: Tue Jan 20, 2004 2:28 am
Location: PDC, Copenhagen Denmark
Contact:

Keyword expansion causes merge conflict

Post by Thomas Linder Puls » Thu Mar 04, 2010 3:57 am

Our source files uses keyword expansion in a string literal:

Code: Select all

constants
    classVersion = "$JustDate: 2010-01-27 $$Revision: 25 $".
Very often when doing a get latest with "Attempt automatic merge" some of the files that get "Needs merge" status only have a conflict in that particular line.

So I have to waste time in investigating this non-conflict and resolving the merge state.

It would be very nice if the automatic merge could handle this.
Thomas Linder Puls
Visual Prolog www.visual-prolog.com

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Keyword expansion causes merge conflict

Post by lbauer » Thu Mar 04, 2010 11:20 am

We have feature request 10032 logged for this functionality; I'll add your vote.
Linda Bauer
SourceGear
Technical Support Manager

Thomas Linder Puls
Posts: 153
Joined: Tue Jan 20, 2004 2:28 am
Location: PDC, Copenhagen Denmark
Contact:

Re: Keyword expansion causes merge conflict

Post by Thomas Linder Puls » Thu Mar 04, 2010 5:43 pm

Fine.
Thomas Linder Puls
Visual Prolog www.visual-prolog.com

Post Reply