From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32420 invoked by alias); 22 Aug 2016 11:54:09 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 32404 invoked by uid 89); 22 Aug 2016 11:54:09 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-92.4 required=5.0 tests=BAYES_50,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_BRBL_LASTEXT,RCVD_IN_PBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC autolearn=ham version=3.3.2 spammy=bills, Bills, collected, neat X-HELO: calimero.vinschen.de Received: from ipbcc0190b.dynamic.kabel-deutschland.de (HELO calimero.vinschen.de) (188.192.25.11) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 22 Aug 2016 11:54:07 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 5182AA804DD; Mon, 22 Aug 2016 13:54:05 +0200 (CEST) Date: Mon, 22 Aug 2016 11:54:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: [ITP] FUSE 2.8 Message-ID: <20160822115405.GA2971@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <579A4102.9040406@maxrnd.com> <20160728200435.GG26311@calimero.vinschen.de> <20160729085141.GK26311@calimero.vinschen.de> <20160817091433.zksukafls6mkk52u@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.2 (2016-07-01) X-SW-Source: 2016-08/txt/msg00072.txt.bz2 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 2506 On Aug 22 02:43, Mark Geisert wrote: > On Wed, 17 Aug 2016, Corinna Vinschen wrote: > > > > Mark, did you find out how to move the repo under the Cygwin org > > > > in the meantime? Is it the "Import repository" functionality by > > > > any chance? > > >=20 > > > Hi Corinna, > > > Bill and I worked it out on a different thread of this conversation. = I > > > currently have a public repo mgeisert/cygfuse on GitHub. That seemed= to be > > > sufficient to me as maintainer. Does it need to be moved under cygwi= n/ ? > > > If yes, it looks like "Import Repository" is a way to do it. > >=20 > > It doesn't *need* to be but it would be neat and helpful to have > > closley Cygwin-related projects in the Cygwin org. >=20 > I don't have any objection to that in principle. It's hard for me to tell > if this project qualifies that way, though. No worries, it's your call. We just provide the Cygwin org for all of us to share. It would be a pity if it goes mostly unused. > Conceptually it's kind of like > a VFS layer, but the core functionality is in Bill's separate Windows-nat= ive > WinFSP dll. The Cygwin end of things is just a bunch of wrappers around > WinFSP calls all collected in a Cygwin dll. (BTW, I don't see how > transparency is supposed to work in a setup like this.) I guess you'd need to discuss this with Bill. > > > I was planning to make sure the package Bill supplied met all the > > > requirements for a Cygwin package. I figure it's real close but ther= e was > > > something I wasn't sure about and needed to research further, then re= al life > > > intervened. Something to do with where its cygport file was getting = package > > > source from. > >=20 > > Directly from git? See, e.g., the cygwin package's cygport. >=20 > OK. The cygfuse.cygport file is referring to Bill's separate GitHub space > for source code. Not sure it ought to do that. Either my GitHub space (= as > I'm the Cygwin cygfuse maintainer) or Cygwin's GitHub space seems better. In theory it doesn't matter, as long as the github space is open to the public and the license is OSS compatible. > I'm debugging some faulting test programs so this cygfuse code doesn't se= em > fully ready for prime time just yet. I'm sure Bill had it working so it's > likely to be some kind of local issue, so it's mine to solve. Ok. Thanks, Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --17pEHd4RhPHOinZp Content-Type: application/pgp-signature; name="signature.asc" Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXuufdAAoJEPU2Bp2uRE+g9HIP/A+QZcALAKhN3LKvIbWMiAHq rPhrIKUwWG+h44xuG2GhweH15W2yiOZlJ2o/5iv4vr9dYOplRxTb7N+YorzIKHRj GUKM+7KDeWeyrYEOUFsHH/YKRbPgxCXBwlcPuXtmF1LySEeWhj3MOfmyqhDZT5w3 mfe36rtMVERhuxj3k+jjZ6nhQZGU0MOVlJUcbITcQxdLua+xU5L+T5b5on8d3A2n YHsPKgFtkibwi7EfX88WHmXnwd3+uCT27x9N+wzu4C4Xlw3isffxlCfAdcq95u06 Y+CG65SDhG7ivWt0pGFj0D/2KOvGlSfkkuJXy7XIClT8jEXWtWb3zv5+Aro7AU5J ZWRef0Uh8Csuojq3NibRknjUb6WkoNmSNbPTyTA/D735dx97iURSAb3viEanb0cD eIbFQ9NCkA7o0pfiZ++OEtCqEjP8jZrzyyAP5/UJVknU+1wtw32jt/JobHMDpXFM QJKaDwBh4Gs7Ms9wgbJRhEFoLJfWzqdMaEwdQ8OQufj9TtCg+YNL55++351qiH54 nu5zj39aOK1Rb55K4oO+NxjklfjN0I9c82qZ7J/zsv4IjDykMqHVmxRmV171ZSV1 dK0+8aOscIxuVvPsNBp0T4Yc+j7maKnMV3uNTf5H3hpLkWwxryBPWbEAd0Tek/Ai wo9g0QprklnDwQe6iAC0 =83hm -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--