public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Re: Most git executables are hard links to git.exe?
Date: Fri, 21 Jul 2023 14:54:08 -0700	[thread overview]
Message-ID: <a5e19263-d820-7737-16eb-16e6429dd586@jhmg.net> (raw)
In-Reply-To: <ba2c0efe-7892-6eb3-9828-ca8d83643939@Shaw.ca>

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?

-- 
Jim Garrison
jhg@acm.org


  reply	other threads:[~2023-07-21 21:54 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 [this message]
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

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=a5e19263-d820-7737-16eb-16e6429dd586@jhmg.net \
    --to=jhg@jhmg.net \
    --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).