From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wen Congyang Subject: Re: [PATCH 00/17] blktap2 related bugfix patches Date: Wed, 15 Oct 2014 09:05:29 +0800 Message-ID: <543DC859.1080207@cn.fujitsu.com> References: <1413252845-23433-1-git-send-email-wency@cn.fujitsu.com> <21565.17844.525542.420665@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <21565.17844.525542.420665@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: Lai Jiangshan , Jiang Yunhong , Dong Eddie , xen devel , Yang Hongyang , Ian Campbell List-Id: xen-devel@lists.xenproject.org On 10/14/2014 11:48 PM, Ian Jackson wrote: > Wen Congyang writes ("[PATCH 00/17] blktap2 related bugfix patches"): >> These bugs are found when we implement COLO, or rebase >> COLO to upstream xen. They are independent patches, so >> post them in separate series. > > blktap2 is unmaintained AFAICT. > > In the last year there has been only one commit which shows evidence > of someone caring even slightly about tools/blktap2/. The last > substantial attention was in March 2013. > > (I'm disregarding commits which touch tools/blktap2/ to fix up compile > problems with new compilers, sort out build system and file > rearrangements, etc.) > > The file you are touching in your 01/17 was last edited (by anyone, at > all) in January 2010. > > Under the circumstances, we should probably take all these changes > without looking for anyone to ack them. > > Perhaps you would like to become the maintainers of blktap2 ? :-) Hmm, I don't have any knowledge about disk format, but blktap2 have such codes(For example: block-vhd.c, block-qcow.c...). I think I can maintain the rest codes. The block-remus related modification should be reviewed and acked by remus maintainers. Thanks Wen Congyang > > Ian. > . >