From: Junio C Hamano <gitster@pobox.com>
To: Matthias Lederhofer <matled@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Makefile: USE_SYMLINK option
Date: Sat, 30 Jun 2007 11:46:52 -0700 [thread overview]
Message-ID: <7v7iplcmar.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070630181456.GA15035@moooo.ath.cx> (Matthias Lederhofer's message of "Sat, 30 Jun 2007 20:14:56 +0200")
Matthias Lederhofer <matled@gmx.net> writes:
> I found no real drawback using symlinks and symlinks are sometimes
> more practical, for example when copying/creating a tarball of the
> installation.
Well, tar handles hard links just fine, thanks. The real
drawbacks of doing symlinks people often cite (and I agree to)
are that they can become dangling, and they consume i-nodes.
prev parent reply other threads:[~2007-06-30 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 18:14 [PATCH] Makefile: USE_SYMLINK option Matthias Lederhofer
2007-06-30 18:46 ` Junio C Hamano [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=7v7iplcmar.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=matled@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.