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

Re: RC1 on Friday (was: Re: SVN 1.5 and RC1)

From: Achim Spangler <Achim.Spangler_at_mnet-online.de>
Date: Wed, 2 Apr 2008 21:30:47 +0200

is there a chance to get issue 3148
( http://subversion.tigris.org/issues/show_bug.cgi?id=3148 ) solved for final

I understood the comment of C. Michael Pilato, as if this would be a
reasonable change/fix/enhancement, and that this shouldn't be too complex.

This would make lists of "svn:externals" better useable, when a subset of
the "svn:externals" is not available/accessible (i.e. retrieve all other
accessible svn:externals resources and simply report the failed ones at the

Am Mittwoch, 2. April 2008 schrieb Mark Phippard:
> On Thu, Mar 27, 2008 at 11:24 AM, Hyrum K. Wright
> <hyrum_wright_at_mail.utexas.edu> wrote:
> > Hyrum K. Wright wrote:
> > > Karl Fogel wrote:
> > > > RC1 this week? :-) Hyrum?
> > >
> > > That works for me. I'm going to be afk for most of the weekend, but
> > > that shouldn't block folks if we roll on Thursday or Friday.
> >
> > STATUS is looking pretty clean, and unless anybody objects, I'm planning
> > to roll RC1 tomorrow morning (03-28-2008 @ 1500 UTC).
> There are a couple of items in STATUS now. Other than that, there is
> just the proposed change to the mergeinfo command line output. I
> think we have reached consensus on the UI change, and decided on the
> minor formatting changes, rather than the bigger "make it look like
> svn log" proposals. Once cmpilato wraps it up, commits it and
> proposes it for backport we should be able to roll RC1 when the STATUS
> file is clean. Probably by Friday I would guess.
> So it might be worth putting out another call to make sure everything
> has been proposed and voted on prior to then.

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-02 21:31:02 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.