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

Re: Subversion 1.5 issues blocking RC1

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Mon, 07 Apr 2008 13:18:04 -0500

Mark Phippard wrote:
> On Mon, Apr 7, 2008 at 9:17 AM, Hyrum K. Wright
> <hyrum_wright_at_mail.utexas.edu> wrote:
>> Mark Phippard wrote:
>>> On Sun, Apr 6, 2008 at 10:33 AM, Mark Phippard <markphip_at_gmail.com> wrote:
>>>> I thought it would be useful to start a new thread where we can gather
>>>> a sort of to-do list of things we need to look at before we can make
>>>> the RC1. We did a lot of work yesterday to get close to the release,
>>>> but there are still some things left to do.
>> ...
>>>> 6) I think I found a bug in log -g when the item has been renamed:
>>>> http://svn.haxx.se/dev/archive-2008-04/0235.shtml
>>>> I think we could fix this later, but it needs to be looked at.
>>>> Hyrum, do you have any time to look at this?
>>>> I think restoring and fixing the mergeinfo API is probably the biggest
>>>> blocker on this list, especially since it bleeds into the bindings
>>>> which need to catch up. Hopefully we can tackle this list quickly and
>>>> get the RC1 wrapped up.
>>> So, great progress already. It seems like we just need to finalize on
>>> the mergeinfo API stuff and we are good to go. Unless someone was
>>> going to try to tackle the log -g problem today.
>> I think I'm that someone. :)
>> I've got a number of other (non-svn) things to take care of today, so it
>> might be this evening before I realistically get a chance to start looking
>> at this.
> Well, FWIW, I do not think it would be the end of the world if this
> fix came in 1.5.1 (or RC2 if we have one).

Honestly, postponing it is probably more realistic at this point. (Of
course, others are free to look at it if the wish!)


Received on 2008-04-07 20:18:23 CEST

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.