Hi Scott,I did not find any mention of this property any where in documentation (could have missed probably) and it looks to me just keeping a history of the commits that are merged back to release branch and I do not see any harm in doing that and certainly its not an extra effort as I think this is handled by the mergefromtrunk script.
Vikas On May 21, 2009, at 2:43 PM, Scott Gray wrote:
Sorry if this is an svn noob question, but what's so great about this mergeinfo file that it's worth the extra effort anyway?Thanks Scott On 21/05/2009, at 9:05 PM, Ashish Vijaywargiya wrote:Hello Jacques,As we all know that we are maintaining the details of revision (trunk revision details that we apply to RB9.04) in the svn:mergeinfo file. But certainly we(Me, Vikas and few others don't have framework and OFBiz root files / folder write access) don't have commit right for that file so most of the time we leave that file as it is.And wait for someone like you to commit the changes later on. What can be the better solution to handle this ?Is it good that we commit the code in release branch and explicitly inform to commit the changes in svn:mergeinfo file ?Please let me know your thoughts on this, as your comment on this will help us not to miss any version info from svn:mergeinfo file after committing the code.Thanks ! -- Ashish
smime.p7s
Description: S/MIME cryptographic signature
