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.
From: email@example.com on behalf of David Glasser
Sent: Fri 12/14/2007 9:28 PM
To: Kamesh Jayachandran
Cc: SVN Dev
Subject: Re: Merging record_exact_merge_and_commit_revs to /trunk
On Dec 14, 2007 7:30 AM, Kamesh Jayachandran <firstname.lastname@example.org> wrote:
> Hi All,
> record_exact_merge_and_commit_revs has extracted the schema related
> changes from issue-2897 branch.
> If there are no objections I will merge that branch back to /trunk
> Upon such a merge one has to dump and load the repositories created with
> older /trunk schema.(No problem for pre-1.5 repositories).
Hi Kamesh. Can you summarize what the problems that are solved by
these schema changes are?
David Glasser | glasser_at_davidglasser.net | http://www.davidglasser.net/
Received on Sat Dec 15 05:50:07 2007