[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Gub/Savannah problem
From: |
David Kastrup |
Subject: |
Re: Gub/Savannah problem |
Date: |
Tue, 17 May 2016 14:28:03 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
"Phil Holmes" <address@hidden> writes:
> ----- Original Message -----
> From: "David Kastrup" <address@hidden>
> To: "Phil Holmes" <address@hidden>
> Cc: "Federico Bruni" <address@hidden>; <address@hidden>
> Sent: Tuesday, May 17, 2016 12:52 PM
> Subject: Re: Gub/Savannah problem
>
>
>> "Phil Holmes" <address@hidden> writes:
>>
>>> No - the double slash was there in my successful build of 2.19.41 - as
>>> I said, I checked and posted that bit of the log file.
>>
>> Update of Git that does no longer like the slash? Or has some other
>> config file?
>
> I can only think that Savannah must have changed something that has
> made that odd syntax illegal, as part of their upgrades. I'm fairly
> sure there was no change in that area at my end.
Well, there _are_ programs at the server end interpreting references as
well. Could be a Git upgrade there causing the problems and/or some
sanitization hooks.
--
David Kastrup
- Re: Gub/Savannah problem, (continued)
- Re: Gub/Savannah problem, David Kastrup, 2016/05/16
- Re: Gub/Savannah problem, Phil Holmes, 2016/05/17
- Re: Gub/Savannah problem, Federico Bruni, 2016/05/17
- Re: Gub/Savannah problem, David Kastrup, 2016/05/17
- Re: Gub/Savannah problem, Phil Holmes, 2016/05/17
- Re: Gub/Savannah problem, David Kastrup, 2016/05/17
- Re: Gub/Savannah problem, Phil Holmes, 2016/05/17
- Re: Gub/Savannah problem, Phil Holmes, 2016/05/17
- Re: Gub/Savannah problem, David Kastrup, 2016/05/17
- Re: Gub/Savannah problem, Phil Holmes, 2016/05/17
- Re: Gub/Savannah problem,
David Kastrup <=