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

RE: Merging record_exact_merge_and_commit_revs to /trunk

From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: 2007-12-15 10:24:23 CET

>On Dec 14, 2007 8:45 PM, Kamesh Jayachandran <kamesh@collab.net> wrote:
>>
>>
>>
>> David,
>>
>> http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=133396 we have
>> decided to port this schema change from issue-2897 branch.
>>
>> With this mergeinfo_changed schema change we have exact merge ranges for a
>> given commit.
>>
>> The idea behind this change is to record *some information* which is very
>> difficult to populate once we release without this schema change.

>I'm confused. Are you suggesting that the reason to merge the schema
>change to trunk now (without the higher-level code that uses it) is so
>that we can release 1.5 with the schema change but without any code
>that uses it?

I am still working on 2897, now I could see a light at the end of the tunnel for this problem.
Last week we did not have this much of a clarity and hence
we thought probably 2897 may slip 1.5(Which I don't think now).
So Mark proposed to extract this schema change alone and record in a separate branch as the information about merges on a commit would be too difficult to populate in the future.

I am ok with either merging 'record_exact_merge_and_commit_revs' to trunk now or as a whole issue-2897 to trunk once done with it.

With regards
Kamesh Jayachandran
Received on Sat Dec 15 10:24:41 2007

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