From: James Gregurich <bayoubengal@mac.com>
To: cygwin-developers@cygwin.com
Subject: Re: utility to update existing cygwin symlinks to native format? (was Re: native symlink)
Date: Mon, 29 Apr 2013 23:49:00 -0000 [thread overview]
Message-ID: <671E245A-BDCD-4F46-90B7-9E73301126C1@mac.com> (raw)
In-Reply-To: <517F061D.5080201@cygwin.com>
On Apr 29, 2013, at 4:45 PM, "Larry Hall (Cygwin Developers)" wrote:
> On 4/29/2013 6:04 PM, James Gregurich wrote:
>> I have not gotten a response to this question yet. I'd like to get into
>> a position to roll this version of cygwin out so that we can use it daily and
>> look for glitches, but I do need the ability to upgrade existing symlinks
>> before that is feasible. Is there an answer to my question?
>
> You'll have to wait until Corinna returns from vacation at least for the
> answer to whether or not this has been done already. I can't say if
> you've inspired Corinna (or someone else) to implement this for you.
> If not, you may have to create your own utility for this part.
>
> --
> Larry
ok. thanks for the info
The utility that I wrote for myself depends upon an exposed API function in path.cc since all the logic to handle the internal format of the cygwin symlink file is contained in path.cc. I could easily write one for myself if such a function were exposed as a public API. I'd just need the specs to use the call.
-James
next prev parent reply other threads:[~2013-04-29 23:49 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 15:17 64 bit Cygwin 1.7.18-12 Corinna Vinschen
2013-03-27 21:54 ` native symlink James Gregurich
2013-03-27 22:41 ` Larry Hall (Cygwin Developers)
2013-03-31 15:55 ` Jeffrey Altman
2013-04-01 16:17 ` Larry Hall
2013-04-01 19:25 ` James Gregurich
2013-04-01 19:52 ` Christopher Faylor
2013-04-01 22:03 ` James Gregurich
2013-04-02 0:06 ` Christopher Faylor
2013-04-03 0:49 ` James Gregurich
2013-04-03 1:41 ` Christopher Faylor
2013-04-03 3:16 ` James Gregurich
2013-04-03 4:33 ` Jeffrey Altman
2013-04-03 15:29 ` Corinna Vinschen
2013-04-03 16:32 ` Larry Hall
2013-04-03 16:51 ` Jeffrey Altman
2013-04-03 16:52 ` Jeffrey Altman
2013-04-03 17:29 ` Corinna Vinschen
2013-04-03 20:46 ` Corinna Vinschen
2013-04-03 21:35 ` Jeffrey Altman
2013-04-11 16:03 ` Corinna Vinschen
2013-04-11 21:55 ` Jeffrey Altman
2013-04-12 8:33 ` Corinna Vinschen
2013-04-13 13:08 ` Jeffrey Altman
2013-04-13 14:54 ` Corinna Vinschen
2013-04-03 21:31 ` James Gregurich
2013-04-24 10:35 ` Corinna Vinschen
2013-04-24 12:06 ` Jeffrey Altman
2013-04-24 12:50 ` Corinna Vinschen
2013-04-24 17:52 ` James Gregurich
2013-04-24 17:56 ` Jeffrey Altman
2013-04-24 18:14 ` Corinna Vinschen
2013-04-24 18:16 ` Jeffrey Altman
2013-04-26 23:39 ` James Gregurich
2013-04-29 22:05 ` utility to update existing cygwin symlinks to native format? (was Re: native symlink) James Gregurich
2013-04-29 23:45 ` Larry Hall (Cygwin Developers)
2013-04-29 23:49 ` James Gregurich [this message]
2013-04-29 23:52 ` James Gregurich
2013-04-30 0:25 ` Christopher Faylor
2013-04-30 0:34 ` James Gregurich
2013-04-30 0:44 ` Charles Wilson
2013-04-30 1:19 ` James Gregurich
2013-05-03 21:53 ` native symlink support should fallback to default format if target missing James Gregurich
2013-05-13 15:00 ` Corinna Vinschen
2013-05-13 15:25 ` Jeffrey Altman
2013-05-13 15:40 ` Corinna Vinschen
2013-05-13 18:59 ` Christopher Faylor
2013-05-13 19:47 ` Earnie Boyd
2013-05-14 14:52 ` James Gregurich
2013-05-14 15:04 ` Corinna Vinschen
2013-05-14 15:54 ` Jeffrey Altman
2013-05-14 16:07 ` Corinna Vinschen
2013-05-14 21:04 ` James Gregurich
2013-05-14 16:42 ` Christopher Faylor
2013-05-14 21:11 ` James Gregurich
2013-05-15 2:28 ` Christopher Faylor
2013-05-15 15:07 ` James Gregurich
2013-05-14 21:04 ` James Gregurich
2013-05-14 15:31 ` Christopher Faylor
2013-05-13 15:00 ` native symlink Corinna Vinschen
2013-05-13 15:12 ` Charles Wilson
2013-05-13 15:39 ` Corinna Vinschen
2013-05-13 20:54 ` Charles Wilson
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=671E245A-BDCD-4F46-90B7-9E73301126C1@mac.com \
--to=bayoubengal@mac.com \
--cc=cygwin-developers@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).