Re: [PATCH] docs: Clarify options that should not have data

To: Wouter Verhelst <w@uter.be>
Cc: Alex Bligh <alex@alex.org.uk>, Eric Blake <eblake@redhat.com>, nbd@other.debian.org
Subject: Re: [PATCH] docs: Clarify options that should not have data
From: Alex Bligh <alex@alex.org.uk>
Date: Thu, 19 Oct 2017 00:13:59 +0200
Message-id: <[🔎] DC5F8F83-A8BF-4638-B8C7-90DCB473B573@alex.org.uk>
In-reply-to: <[🔎] 20171018200334.zcfgjfno74u6icul@grep.be>
References: <[🔎] 20171018194012.31951-1-eblake@redhat.com> <[🔎] 20171018200334.zcfgjfno74u6icul@grep.be>

> On 18 Oct 2017, at 22:03, Wouter Verhelst <w@uter.be> wrote:
> 
> It seems to me that you've been pesky enough with all these
> documentation patches, that you should be punished for it with commit
> access ;-)

+1. Sorry I have not had time to look at these immediately. I
had this queued up for the weekend in 9 days time, but Wouter
probably just saved me the effort :-)

-- 
Alex Bligh

Reply to:

References:
- [PATCH] docs: Clarify options that should not have data
  - From: Eric Blake <eblake@redhat.com>
- Re: [PATCH] docs: Clarify options that should not have data
  - From: Wouter Verhelst <w@uter.be>

Prev by Date: [PATCH] docs: Clarify that some options should be send-once
Next by Date: Re: [PATCH] docs: Clarify that some options should be send-once
Previous by thread: Re: [PATCH] docs: Clarify options that should not have data
Next by thread: [PATCH] docs: Clarify that some options should be send-once
Index(es):
- Date
- Thread