bug in HTTP protocol spec

2018-02-21 Thread Dorian Taylor
#L279 (Note these links are from the most recent commit of this file as of this writing.) Just thought somebody would like to know. Regards, -- Dorian Taylor Make things. Make sense. https://doriantaylor.com

Re: bug in HTTP protocol spec

2018-02-21 Thread Dorian Taylor
ce=$servicename" LF) *1("version 1") +"" ref_list "" ref_list = empty_list / non_empty_list -- Dorian Taylor Make things. Make sense. https://doriantaylor.com

Re: bug in HTTP protocol spec

2018-02-21 Thread Dorian Taylor
> On Feb 21, 2018, at 9:37 PM, Jonathan Nieder wrote: > > Thanks for writing it. > > Do you mind if we forge your sign-off? (See Documentation/SubmittingPatches > item '(5) Certify your work' for details about what this means.) Sure, or I can just re-paste:

Re: bug in HTTP protocol spec

2018-02-22 Thread Dorian Taylor
of that submitGit thing that is advertised when you try to open a pull request on the git repository on Github. I was a bit surprised myself. -- Dorian Taylor Make things. Make sense. https://doriantaylor.com signature.asc Description: Message signed with OpenPGP using GPGMail

Re: bug in HTTP protocol spec

2018-02-22 Thread Dorian Taylor
l endpoint and found it contained content that didn’t agree with the spec. I then obliged the request to submit a patch with *what I knew to be true* about the sample that actually worked. I then followed the recommendations *advertised on GitHub* for submitting the patch. You’re welcome. -