From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [QUAR] execfuse
Date: Sat, 7 May 2022 12:41:32 -0600 [thread overview]
Message-ID: <5bd5b62e-0792-1ace-552c-3404ad0ea093@SystematicSw.ab.ca> (raw)
In-Reply-To: <CA+7cx1otD5X02e6sFLnAyV_rN5owKpHG_EFyT6afGC95KYMQdA@mail.gmail.com>
On 2022-05-07 11:47, Morten Kjærulff wrote:
> On Fri, May 6, 2022, 17:52 Eliot Moss wrote:
>> On 5/6/2022 11:42 AM, Morten Kjærulff wrote:
>>> Do you think it would be possible to port this to cygwin?
>>> https://github.com/vi/execfuse
>> I'm thinking"Probably, since some version of fuse is
>> available." However, Cygwin relies on volunteer labor,
>> so either you dive in yourself or convince someone to
>> do it.
> Unless someone else takes this, I will see if I can find time and find out.
> It will be my first contribution. I am a long time cygwin user, so I will
> be glad if I can help.
> My own first usecase will be my ~/.netrc, which I will "convert" to a
> script that gpg decrypt an encrypted version of my netrc file.
If you use curl, *ftp, wget, wget2, test those to see if access still
works properly.
Good luck.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2022-05-07 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 15:42 execfuse Morten Kjærulff
2022-05-06 15:52 ` [QUAR] execfuse Eliot Moss
2022-05-07 17:47 ` Morten Kjærulff
2022-05-07 18:41 ` Brian Inglis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bd5b62e-0792-1ace-552c-3404ad0ea093@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).