[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: Mark Phippard <markphip_at_gmail.com>
Date: 2007-12-15 13:43:18 CET

On Dec 15, 2007 1:19 AM, David Glasser <glasser@davidglasser.net> wrote:
> 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?

The schema change captures mergeinfo that would be hard to go back and
recreate in 1.6 if we do not start capturing it now. I suggested that
Kamesh extract out the schema change and the code that populates the
table so that we would have the OPTION of including it in 1.5 if his
other work did not make it AND we concluded that this extra
information was going to eventually be essential.

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 15 13:43:29 2007

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.