Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mail-b.sr.ht (Postfix) with ESMTPS id EB24FFF104 for <~nhanb/mcross-announce@lists.sr.ht>; Fri, 11 Sep 2020 15:19:13 +0000 (UTC) Authentication-Results: mail-b.sr.ht; dkim=pass (2048-bit key) header.d=imnhan.com header.i=@imnhan.com header.b=d2SrzcEW; dkim=fail reason="key not found in DNS" (0-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b=Vxfdsd2A Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id B95CB5C0256; Fri, 11 Sep 2020 11:19:13 -0400 (EDT) Received: from imap35 ([10.202.2.85]) by compute3.internal (MEProxy); Fri, 11 Sep 2020 11:19:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imnhan.com; h= mime-version:message-id:date:from:to:cc:subject:content-type :content-transfer-encoding; s=fm1; bh=B4RCNV0Mg9/YkSkSLCC/hUKU7y KEpeCENxpyDvN93Sw=; b=d2SrzcEWmtaP3u5PHkr/WJ/CDeVjBb8OOFV2nk4zEF l/cfFVCFJnqdyQou3PI0Tj/9WWEz8UxpbZ+mtCKOsWMa4nf53uOuUcGInvi7XPd+ zLF82K1wl8Oik5EiWOjH78jbbVs1fKEY0nTNDTvRQ6UF3ef0isx3u3AMcfNAuY73 HE0k41SRI7krwd2BSuYVkKZD/fbmd3UnItiAOKCOMUFNRZvOgPKg9rfDWvG2GGaw 7b6kpvqGfHqmJKdLyuRva/8N6mPg0aYe1vN2mc5bdkA2izKlXelp2pe3MKnpdE7c uowjve6saJIvGdi88wtH5+H0cgE2N1qVFJHWLjNcqX/Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=B4RCNV 0Mg9/YkSkSLCC/hUKU7yKEpeCENxpyDvN93Sw=; b=Vxfdsd2ABoV0S8G79MASHI 9sNycKNVz0/g22udyMZyo/sa384tz0ZhjDzcqLWGkLPqm42mgZjSsQc16mi/1SDX X/NepUCiE0ievV4awFGjj1cJbB9WvXXchPn4hneXK+msuYY9qOxY918tT7Dc4XOV 07ES9jvdn34GhRO3xbDtO4MRS7F8FnBo44cIKgtUUVrQLqjXYaRHN+CcNrdHb8PF nrcBFuuBl5MSBQFXYIkniZf9stR3QuLW9TIfdgEUABV0QWQq117FcCZpsdBJ1Ijr lK97/zH+QylIjwuQ1PGuv1AZn1GQsq1nAVLqn7gl2ZISCTbP88mTeyyqTkMGLyXw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudehledgkeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtgfesthhqre dtreerjeenucfhrhhomhepuepqihgpvfhhiohnhhgppfhhkohnuceohhhisehimhhnhhgr nhdrtghomheqnecuggftrfgrthhtvghrnhepgfevfffggfdtkefgudffkeeijeeutedvff euueefhfetueeludfhjeegteehleelnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhephhhisehimhhnhhgrnhdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6F00514C08D4; Fri, 11 Sep 2020 11:19:12 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.3.0-259-g88fbbfa-fm-20200903.003-g88fbbfa3 Mime-Version: 1.0 Message-Id: Date: Fri, 11 Sep 2020 22:19:20 +0700 From: =?UTF-8?Q?B=C3=B9i_Th=C3=A0nh_Nh=C3=A2n?= To: ~nhanb/mcross-announce@lists.sr.ht Cc: "Frederick Yin" Subject: Re: McRoss distribution Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Yin, > (3) I rename my fork "picross" which means a sort of puzzle involving > arranging pixels into a picture I vote for option (3). Though I don't have the spare capacity for McRoss= development now, I do wish to come back to it from time to time at my own pace. Honestly I'm too lazy to review patches now, and at the same time I don't want to block others (that is, you) from further development so a separate fork makes the most sense to me. I quite like the McRoss name, so I hope you don't mind me clinging to it :) Cheers, Nh=C3=A2n