Re: [PATCH v3] http-backend: allow empty CONTENT_LENGTH

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v3] http-backend: allow empty CONTENT_LENGTH
From: Max Kirillov <max@xxxxxxxxxx>
Date: Mon, 10 Sep 2018 23:36:28 +0300
Cc: Max Kirillov <max@xxxxxxxxxx>, Jelmer Vernooĳ <jelmer@xxxxxxxxx>, git@xxxxxxxxxxxxxxx, Jeff King <peff@xxxxxxxx>
In-reply-to: <20180910051748.GA55941@aiede.svl.corp.google.com>
References: <20180908001940.GB225427@aiede.svl.corp.google.com> <20180908054224.21856-1-max@max630.net> <20180910051748.GA55941@aiede.svl.corp.google.com>
User-agent: Mutt/1.5.23 (2014-03-12)

On Sun, Sep 09, 2018 at 10:17:48PM -0700, Jonathan Nieder wrote:
> From: Max Kirillov <max@xxxxxxxxxx>
> Subject: http-backend test: make empty CONTENT_LENGTH test more realistic

Thank you, yes, this is what should have left

Follow-Ups:
- Re: [PATCH v3] http-backend: allow empty CONTENT_LENGTH
  - From: Jonathan Nieder

References:
- Re: [PATCH v2] http-backend: allow empty CONTENT_LENGTH
  - From: Jonathan Nieder
- [PATCH v3] http-backend: allow empty CONTENT_LENGTH
  - From: Max Kirillov
- Re: [PATCH v3] http-backend: allow empty CONTENT_LENGTH
  - From: Jonathan Nieder

Prev by Date: Re: [PATCH v2 10/11] builtin rebase: only store fully-qualified refs in `options.head_name`
Next by Date: [PATCH] http-backend: Treat empty CONTENT_LENGTH as zero
Previous by thread: Re: [PATCH v3] http-backend: allow empty CONTENT_LENGTH
Next by thread: Re: [PATCH v3] http-backend: allow empty CONTENT_LENGTH
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux