Okay. I just pushed something. I did a simple test and made sure the
newlines aren't there. Can you check if it works for you in your
specific scenario?
Jay
On Fri, May 8, 2015 at 6:31 AM, Tim Brown wrote:
> Jay,
>
> I agree with Greg, too. For me, that involves abandoning my patch, and
> a whol
I agree with Greg, that seems like the right thing. Tim, do you want
to make a pull request or do you want me to just take care of it?
Jay
On Thu, May 7, 2015 at 2:59 PM, Greg Hendershott
wrote:
> That sounds good. Although I haven't used it in awhile, I recall needing to
> slice that off more o
Jay,
Thank you.
On 08/05/15 11:42, Jay McCarthy wrote:
Okay. I just pushed something. I did a simple test and made sure the
newlines aren't there. Can you check if it works for you in your
specific scenario?
That seems to do the trick for me.
My web-server challenges my Firefox, which in turn
Jay,
I agree with Greg, too. For me, that involves abandoning my patch, and
a whole load of git admin the sum of which effort is greater than you
just doing it. So, please do and reject my pull request (if you can).
Regards,
Tim
On 08/05/15 11:20, Jay McCarthy wrote:
I agree with Greg, that s
That sounds good. Although I haven't used it in awhile, I recall needing to
slice that off more often than keeping it.
On May 7, 2015 2:22 PM, "Tim Brown" wrote:
> I wonder if base64-encode should rather be patched with a #:last-newline?
> (Default #t) argument.
>
> Tim
>
> On 7 May 2015 17:37:18
I wonder if base64-encode should rather be patched with a #:last-newline?
(Default #t) argument.
Tim
On 7 May 2015 17:37:18 BST, Tim Brown wrote:
>Folks,
>
>I've just tried to use web-server/http-digest-auth, and
>it seems that make-digest-auth-header generates an invalid header
>(or at least o
6 matches
Mail list logo
