From: Andrey Repin <anrdaemon@yandex.ru>
To: Jim Garrison via Cygwin <jhg@acm.org>, cygwin@cygwin.com
Subject: Re: Most git executables are hard links to git.exe?
Date: Mon, 31 Jul 2023 16:36:45 +0300 [thread overview]
Message-ID: <1792659841.20230731163645@yandex.ru> (raw)
In-Reply-To: <a5e19263-d820-7737-16eb-16e6429dd586@jhmg.net>
Greetings, Jim Garrison via Cygwin!
> On 07/21/23 14:52, Brian Inglis wrote:
>> On 2023-07-21 14:59, Jim Garrison via Cygwin wrote:
>>> Git comes with over 100 executables, mostly in /usr/libexec/git-core,
>>> that all appear to be *hard* links to /bin/git, in both Cygwin and
>>> Windows. The Windows fsutil command shows they're all hard linked:
> [snip]
>>> I'm curious to know if there's a specific reason for this implementation
>>> that would make it the choice over symbolic links.
>> > For the same reason you are complaining about backups not taking > hardlinks into account: to avoid distributing 400MB instead of 3MB.
>> > Cygwin backup utilities should be able to deal with these e.g. rsync -H, > --hard-links, although it appears xcopy and robocopy may not under > Windows 10; don't know about other utilities or Windows 11.
> But why not use symbolic links to accomplish the same thing?
Adding to the bullet list:
cmd's handling of symbolik links is such that given a symlink path, it would
actually execute the symlink target, thoroughly ruining the executable name
and associated CWD. Making them unusable as command processors in general.
--
With best regards,
Andrey Repin
Monday, July 31, 2023 16:33:49
Sorry for my terrible english...
prev parent reply other threads:[~2023-11-06 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 20:59 Jim Garrison
2023-07-21 21:52 ` Brian Inglis
2023-07-21 21:54 ` Jim Garrison
2023-07-22 5:55 ` Larry
2023-07-22 17:33 ` Adam Dinwoodie
2023-07-22 17:35 ` Jim Garrison
2023-07-30 0:32 ` L A Walsh
2023-07-31 13:36 ` Andrey Repin [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=1792659841.20230731163645@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=jhg@acm.org \
/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).