Re: Changes to SVN proper that have occurred since move to Git

2019-06-01 Thread sebb
FTR jcs has also now been sorted On Sun, 26 May 2019 at 15:27, sebb wrote: > > I think all but jcs have now been dealt with. > > On Sun, 26 May 2019 at 13:28, sebb wrote: > > > > Forgot to say that I have yet to check the commons-* trees (commons-build > > etc) > > > > On Sun, 26 May 2019 at

Re: Changes to SVN proper that have occurred since move to Git

2019-05-26 Thread sebb
I think all but jcs have now been dealt with. On Sun, 26 May 2019 at 13:28, sebb wrote: > > Forgot to say that I have yet to check the commons-* trees (commons-build etc) > > On Sun, 26 May 2019 at 13:13, sebb wrote: > > > > I've done a comparison of the latest SVN revision with the most recent

Changes to SVN proper that have occurred since move to Git

2019-05-26 Thread sebb
I've done a comparison of the latest SVN revision with the most recent trunk(master) Git entry that includes a line of the following form: git-svn-id: https://svn-us.apache.org/repos/asf/commons/proper/jexl/trunk@1821853 13f79535-47bb-0310-9956-ffa450edef68 AFAICT any discrepancies mean that the

Re: Changes to SVN proper that have occurred since move to Git

2019-05-26 Thread sebb
Forgot to say that I have yet to check the commons-* trees (commons-build etc) On Sun, 26 May 2019 at 13:13, sebb wrote: > > I've done a comparison of the latest SVN revision with the most recent > trunk(master) Git entry that includes a line of the following form: > git-svn-id: >