On Mon, Dec 10, 2018 at 9:10 PM Tom Browder wrote:
>
>
>
> On Mon, Dec 10, 2018 at 19:45 Nico Kadel-Garcia wrote:
>>
>> On Mon, Dec 10, 2018 at 5:56 AM Tom Browder wrote:
>> >
>> > On Mon, Dec 10, 2018 at 12:10 AM Nico Kadel-Garcia
>> > wrote:
>> > > On Sun, Dec 9, 2018 at 6:31 PM Tom Browder
On Mon, Dec 10, 2018 at 19:45 Nico Kadel-Garcia wrote:
> On Mon, Dec 10, 2018 at 5:56 AM Tom Browder wrote:
> >
> > On Mon, Dec 10, 2018 at 12:10 AM Nico Kadel-Garcia
> wrote:
> > > On Sun, Dec 9, 2018 at 6:31 PM Tom Browder
> wrote:
> > ...
> > > > Given that history will be lost, does anyone
On Mon, Dec 10, 2018 at 5:56 AM Tom Browder wrote:
>
> On Mon, Dec 10, 2018 at 12:10 AM Nico Kadel-Garcia wrote:
> > On Sun, Dec 9, 2018 at 6:31 PM Tom Browder wrote:
> ...
> > > Given that history will be lost, does anyone see any problems with my
> > > recovery plan?
> ...
> > If you have wor
On Mon, Dec 10, 2018 at 15:56 Stefan Sperling wrote:
...
Thank you, Stefan!
Best regards,
-Tom
On Mon, Dec 10, 2018 at 03:37:46PM -0600, Tom Browder wrote:
> On Mon, Dec 10, 2018 at 4:55 AM Tom Browder wrote:
> >
> > On Mon, Dec 10, 2018 at 12:10 AM Nico Kadel-Garcia wrote:
> > > On Sun, Dec 9, 2018 at 6:31 PM Tom Browder wrote:
> > ...
> > > > Given that history will be lost, does anyone
On Mon, Dec 10, 2018 at 4:55 AM Tom Browder wrote:
>
> On Mon, Dec 10, 2018 at 12:10 AM Nico Kadel-Garcia wrote:
> > On Sun, Dec 9, 2018 at 6:31 PM Tom Browder wrote:
> ...
> > > Given that history will be lost, does anyone see any problems with my
> > > recovery plan?
> ...
> > If you have wor
On Mon, Dec 10, 2018 at 5:14 AM Stefan Sperling wrote:
> Perhaps Github's customers will just need to press a little bit
> harder for a fix to be applied at Github's end?
Agreed. The squeaky wheel gets the grease.
On 10.12.2018 10:08, Thorsten Schöning wrote:
> Guten Tag Branko Čibej,
> am Sonntag, 9. Dezember 2018 um 19:27 schrieben Sie:
>
>> My current thinking is that if GitHub can't fix their protocol emulation
>> by the time of the planned Subversion 1.12 release, we'll have to
>> seriously consider inc
Let me translate it for English people.
>
>-Original Messages-
>From:"为呐☆而狂"
>Sent Time:2018-12-09 01:01:49 (Sunday)
>To: users
>Cc:
>Subject: [CASS SPAM]Subversion Exception!
>
>Hello:
>
> I installed Tortoise SVN in the C:\Program Files\TortoiseSVN directory, but
> it was not
Hello:
I installed Tortoise SVN in the C:\Program Files\TortoiseSVN directory, but it
was not loaded into the D disk at all. How can I report this error?
---
Subversion Exception!
---
Subversion??
On Mon, Dec 10, 2018 at 12:10 AM Nico Kadel-Garcia wrote:
> On Sun, Dec 9, 2018 at 6:31 PM Tom Browder wrote:
...
> > Given that history will be lost, does anyone see any problems with my
> > recovery plan?
...
> If you have working copies and you don't care about history, why are
> you spending
On Mon, Dec 10, 2018 at 10:08:10AM +0100, Thorsten Schöning wrote:
> If you come to the conclusion that you don't do this kind of hacking
> anymore or even at all including this issue, users of the SVN-bridge
> would simply need to change their workflow to something else. I'm
> only using the bridg
Guten Tag Branko Čibej,
am Sonntag, 9. Dezember 2018 um 19:27 schrieben Sie:
> My current thinking is that if GitHub can't fix their protocol emulation
> by the time of the planned Subversion 1.12 release, we'll have to
> seriously consider including this patch.
If they really didn't fix it until
13 matches
Mail list logo
