git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cedric Staniewski <cedric@gmx.ca>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add NO_CROSS_DIRECTORY_HARDLINKS support to the Makefile
Date: Mon, 11 May 2009 18:29:52 +0200	[thread overview]
Message-ID: <4A085280.3090501@gmx.ca> (raw)
In-Reply-To: <alpine.DEB.1.00.0905111256580.4973@intel-tinevez-2-302>

Johannes Schindelin wrote:
> 	I do not understand how this commit could be responsible, but here 
> 	is an attempt to fix things.

The important difference is that before this commit, git-add was
hardlinked to a file outside of DESTDIR. Thus, when the build directory
was removed or you tar'ed DESTDIR, git-add was just a regular file and
all the other builtins were hardlinked to it.

Behavior before commit:
$ touch git git-add && mkdir bin libexec && cp git bin &&
ln git-add libexec/ &&                      ###  the relevant line
tar caf git.tar.gz bin libexec && tar tfv git.tar.gz

bin/
bin/git
libexec/
libexec/git-add


Behavior after commit:
$ touch git git-add && mkdir bin libexec && cp git bin &&
ln bin/git libexec/git-add &&               ### the relevant line
tar caf git.tar.gz bin libexec && tar tfv git.tar.gz

bin/
bin/git
libexec/
libexec/git-add link to bin/git

  reply	other threads:[~2009-05-11 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 10:41 Cross-directory hard links Cedric Staniewski
2009-05-11 11:02 ` [PATCH] Add NO_CROSS_DIRECTORY_HARDLINKS support to the Makefile Johannes Schindelin
2009-05-11 16:29   ` Cedric Staniewski [this message]
2009-05-11 19:08     ` Johannes Schindelin
2009-05-11 20:05       ` Cedric Staniewski
2009-05-11 16:40 ` Cross-directory hard links Tony Finch

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=4A085280.3090501@gmx.ca \
    --to=cedric@gmx.ca \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.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 NNTP newsgroup(s).