public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Follow-up to: vboxsharedfs - Too many levels of symbolic links
Date: Sun, 2 Jan 2022 00:33:29 +0100	[thread overview]
Message-ID: <2d5959c2-e9a8-bff8-0bf0-533e4787c669@gmail.com> (raw)
In-Reply-To: <25040.56638.44943.834427@consult.pretender>

On 02.01.2022 00:01, cygwin@kosowsky.org wrote:
> Hi,
> About a month ago, a thread with the above title mentioned that a
> patch to the problem was submitted.
> 
> I am encountering the same problem on my Cygwin/Win10/Vbox 6.1.30
> installation.
> 
> Any idea when that patch will be pushed to production?
> Or barring that, is there a test version that I could download
> somewhere as this bug is somewhat limiting for me at this point...
> 

Snapshots are here:
https://cygwin.com/snapshots/


  reply	other threads:[~2022-01-01 23:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01 23:01 cygwin
2022-01-01 23:33 ` Marco Atzeri [this message]
     [not found]   ` <25041.20371.400483.42141@consult.pretender>
2022-01-02  7:12     ` Marco Atzeri

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=2d5959c2-e9a8-bff8-0bf0-533e4787c669@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).