I'm sorry, but I don't see a single whitespace change in this patch.
Also, I didn't know what were the project policies, but the content of
the initial email is summed up in the commit message on top of the
Maybe you want me to send the patch as embedded text in this mail, or
with attachment is enough ?


2014-12-02 21:40 GMT+01:00 Max Kellermann <m...@duempel.org>:
> On 2014/12/02 14:05, X Ryl <boite.pour.s...@gmail.com> wrote:
>> As the subject says, this patch adds support for optional headers for
>> the HTTP output plugins. These headers are required for allowing cross
>> origin resource sharing (for one, but it can be used in reverse proxy
>> mode to identify the server sources).
>> This makes possible to receiving the HTTP stream asynchronously in
>> Javascript, and as such to lower the latency when playing the stream
>> in a web browser / javascript based audio player.
>> It also fix a bug with escaped chars not processed as described in the
>> config file's tokenizer.
> I find it too difficult to read your patch, due to many pointless
> whitespace changes.  Please strip those out.
> Oh, and a patch submission should not need an explanation email.  If
> you need email text, then your commit message is too short.
mpd-devel mailing list

Reply via email to