X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 491423858413
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1690677250;
	bh=33g8BCWSCOl94zVR36c1HSzw6qwkobEwdLSYAp9SRrQ=;
	h=Date:To:CC:Subject:References:In-Reply-To:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 From:Reply-To:From;
	b=F0XACQzG7ByoG3x14Q6B82cbuw7z/YSf4VbKbMXY0TxzyDaeMB1gJVhx1GevlLKh2
	 6Xnl+/nVCfGFB5Y/XAN13zdEZVh0a4WYWz+cUQhnbai6zviaV0j5apaA9IWulCC9Xf
	 2RpCmd+4wPNoSFxaYuVYyDrlmAS/R+b7jleQMp6k=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org AB0AD3858D32
Message-ID: <64C5AFB3.3010508@tlinx.org>
Date: Sat, 29 Jul 2023 17:32:51 -0700
User-Agent: Thunderbird
MIME-Version: 1.0
To: jhg AT acm DOT org
CC: cygwin AT cygwin DOT com, Jim Garrison <jhg AT jhmg DOT net>
Subject: Re: Most git executables are hard links to git.exe?
References: <a243a980-66ba-e01e-298a-60a221efd7b4 AT jhmg DOT net>
 <ba2c0efe-7892-6eb3-9828-ca8d83643939 AT Shaw DOT ca>
 <a5e19263-d820-7737-16eb-16e6429dd586 AT jhmg DOT net>
 <CA+kUOa=PaUHpv6cyJnwab_cRxZz9+b+=P-vkzUtnk7SSvXce2g AT mail DOT gmail DOT com>
 <b917ab75-94d4-fae2-0a50-65b2ca3c82bf AT jhmg DOT net>
In-Reply-To: <b917ab75-94d4-fae2-0a50-65b2ca3c82bf@jhmg.net>
X-Spam-Status: No, score=-16.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 KHOP_HELO_FCRDNS, SPF_HELO_NONE, TXREP, T_SCC_BODY_TEXT_LINE,
 T_SPF_PERMERROR autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: L A Walsh via Cygwin <cygwin AT cygwin DOT com>
Reply-To: L A Walsh <cygwin AT tlinx DOT org>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

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).



-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple