public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Meyer <dmeyer@dmeyer.net>
To: cygwin@cygwin.com
Subject: Re: bash from local mounted drive with subst command
Date: Mon, 19 Sep 2022 16:40:27 -0400	[thread overview]
Message-ID: <CADbUtVMczCCj5Fmk5VF03Y7aTchzOb8j5K-Ssay=BnvupW780A@mail.gmail.com> (raw)

We're running into this same issue on my project.  We're trying to
shorten path names to get around Visual Studio limitations in path
lengths, which are unfortunately very long for us since we're
generating filenames based on package names and the like.

If subst won't work to let us shorten path names, is there any other
solution?  We'd really like something that behaves like bind mounts
rather than symlinks.

Thanks.

             reply	other threads:[~2022-09-19 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 20:40 David Meyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-20 21:38 Claude TETE
2022-02-20 23:41 ` Takashi Yano
2022-02-20 23:56   ` Takashi Yano
2022-02-21  0:05     ` Thomas Wolff
2022-02-21  0:40       ` Takashi Yano
2022-02-21 11:13         ` Corinna Vinschen
2022-03-07 19:36 ` Andrey Repin

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='CADbUtVMczCCj5Fmk5VF03Y7aTchzOb8j5K-Ssay=BnvupW780A@mail.gmail.com' \
    --to=dmeyer@dmeyer.net \
    --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).