Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: error (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=btopenworld.com;
  h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=THc/krpD4s5MYOIBd9gBG/tuuJMBaHEB62UtXo4x0PqmI7T74rYid5oRDOiYXVSdpPd0mopKZabo8vnekr10ETr6+Ts4o6qPOk3HCFf6QCATrp/M4msVQI0cTFofdHt1rMfB9OBWlqQxfGagroVj3VkgkAnPaNmXbWrXJpBChMY=;
References: 
 <CABw-3YfRsVGCN9fWx8AZ1DGyx7F-EBHSGOjZ0-nNLdaUUDRhzQ@mail.gmail.com>
Message-ID: <1370363373.58256.YahooMailNeo@web186105.mail.ir2.yahoo.com>
Date: Tue, 4 Jun 2013 17:29:33 +0100 (BST)
From: Julian Foad <julianfoad@btopenworld.com>
Reply-To: Julian Foad <julianfoad@btopenworld.com>
Subject: Re: Mixed revision working copy check when merging
To: Ivan Zhakov <ivan@visualsvn.com>
Cc: Subversion Development <dev@subversion.apache.org>
In-Reply-To: 
 <CABw-3YfRsVGCN9fWx8AZ1DGyx7F-EBHSGOjZ0-nNLdaUUDRhzQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Ivan Zhakov wrote:=0A=0A> The only problem that checks for mixed revision w=
orking copy performed=0A> at the last stage. Considering the fact that user=
s got mixed revision=0A> after every commit it's very annoying to wait whil=
e svn merge contacts=0A> server, asks for merge info and etc just to show e=
rror that you have=0A> mixed revision working copy. I changed this behavior=
 in r1488183 to=0A> check working copy as soon as possible.=0A> =0A> Change=
 is very simple. I think it should be merged before next RC=0A> otherwise S=
ubversion 1.8.0 could get very bad perception from users.=0A=0AYou're basic=
ally asking for people to approve the back-port proposal for r1488183.=A0 O=
K, Philip and I have now done that.=A0 It's approved.=A0 Thanks for proddin=
g.=0A=0A- Julian