On Mon, Sep 3, 2018 at 6:31 PM Branko Čibej wrote:
> These cases are, believe it or not, completely different. On your Mac,
> the shell expands the wildcards. On Windows, Subversion is linked with a
> library that's shipped with Visual Studio (setargv.obj) that expands the
> wildcards in the
On 03.09.2018 22:30, Nathan Hartman wrote:
> On Mon, Sep 3, 2018 at 11:10 AM Johan Corveleyn wrote:
>
>> On Sun, Sep 2, 2018 at 11:10 PM Nathan Hartman
>> wrote:
>>> I've encountered weirdness with wildcards several times today, so I
>>> just tried in a clean freshly checked-out copy:
>>>
>>>
On Mon, Sep 3, 2018 at 11:10 AM Johan Corveleyn wrote:
> On Sun, Sep 2, 2018 at 11:10 PM Nathan Hartman
> wrote:
> > I've encountered weirdness with wildcards several times today, so I
> > just tried in a clean freshly checked-out copy:
> >
> > E:\workspace\processor>svn rm *.hconfig
> > svn:
Paul Hammant wrote on Sun, 02 Sep 2018 19:30 +:
> I'm not sure if there's a online definitive error guide for Svn, but
> if there is the page for E170013 could be enhanced to suggest "check
> your darn proxy settings in ~/.subversion/servers, fool" (or less
> Paul-centric language).
We should
On Sun, Sep 2, 2018 at 11:10 PM Nathan Hartman wrote:
>
> Has there been a recent change to how wildcards (the asterisk '*') is
> treated under Windows?
>
> I am using command line client 1.10.2 r1835932 as installed with
> TortoiseSVN 1.10.1, Build 28295 - 64 Bit , 2018/07/15 12:14:12, on
>
Ben Reser had previously written a "svn-diff to JSON" thing in Python that
worked very well -
https://stackoverflow.com/questions/20381507/whats-the-best-way-to-turn-a-subversion-diff-into-json
I'm homebrew installing Subversion 1.10 and although there are Python
bindings (the --with-python flag
