From: L A Walsh <cygwin@tlinx.org>
To: jhg@acm.org
Cc: cygwin@cygwin.com, Jim Garrison <jhg@jhmg.net>
Subject: Re: Most git executables are hard links to git.exe?
Date: Sat, 29 Jul 2023 17:32:51 -0700 [thread overview]
Message-ID: <64C5AFB3.3010508@tlinx.org> (raw)
In-Reply-To: <b917ab75-94d4-fae2-0a50-65b2ca3c82bf@jhmg.net>
On 2023/07/22 10:35, Jim Garrison via Cygwin wrote:
> On 07/22/23 10:33, Adam Dinwoodie wrote:
>
>> On Fri, 21 Jul 2023 at 22:54, Jim Garrison via Cygwin wrote:
>>
>>> 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.
>>>>>
The hardlink implementation on windows is very similar to the
implementation on linux. I'm pretty sure that utils that want to save
on space will look at the inode-number and notice that the hardlinked files
all have the same inode-number (windows has a similar concept though it is
called something else).
On linux, utils that are ignorant of inode numbers, will see hardlinked
files
as separate files -- just as windows does.
The symlink files will break if their targets move (same on lin+win).
next prev parent reply other threads:[~2023-07-30 0:33 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 [this message]
2023-07-31 13: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=64C5AFB3.3010508@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
--cc=jhg@acm.org \
--cc=jhg@jhmg.net \
/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).