On Fri, Aug 09, 2013 at 02:01:53AM +0900, Hiroki Sato wrote:
> I think this logic is unnecessarily complex. svnversion does not
> need to run twice, at least.
>
svnversion is only invoked the first time on the newvers.sh file, so the
impact is minimal.
> How about the attached patch?
>
I h
Glen Barber wrote
in <201308081559.r78fx1h6034...@svn.freebsd.org>:
gj> Author: gjb
gj> Date: Thu Aug 8 15:59:00 2013
gj> New Revision: 254094
gj> URL: http://svnweb.freebsd.org/changeset/base/254094
gj>
gj> Log:
gj> When newvers.sh is run, it is possible that the svnversion
gj> (or svnlit
On Thursday, August 08, 2013 11:59:01 am Glen Barber wrote:
> Author: gjb
> Date: Thu Aug 8 15:59:00 2013
> New Revision: 254094
> URL: http://svnweb.freebsd.org/changeset/base/254094
>
> Log:
> When newvers.sh is run, it is possible that the svnversion
> (or svnliteversion) in the current lo
Author: gjb
Date: Thu Aug 8 15:59:00 2013
New Revision: 254094
URL: http://svnweb.freebsd.org/changeset/base/254094
Log:
When newvers.sh is run, it is possible that the svnversion
(or svnliteversion) in the current lookup path is not what
was used to check out the tree. If an incompatible
