From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Jacob Helwig <jacob.helwig@gmail.com>,
Kjetil Barvik <barvik@broadpark.no>,
"Randal L. Schwartz" <merlyn@stonehenge.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: "make quick-install-man" broke recently
Date: Mon, 17 Aug 2009 10:09:10 -0700 [thread overview]
Message-ID: <7vhbw6weo9.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.2.01.0908170932390.3162@localhost.localdomain> (Linus Torvalds's message of "Mon\, 17 Aug 2009 09\:34\:23 -0700 \(PDT\)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> Grr. Now 'check_path()' is no longer something generically useful.
>
> Could you perhaps instead only change 'checkout_entry()' to do this hack,
> and leave 'check_path()' as a generic replacement for "lstat()" that
> doesn't follow symlinks?
Given that non-empty base_dir is only used for "checkout-index --prefix",
iow, the "path" internally used by git and fed to our symlink.c cache are
supposed to be always relative to the work tree, I think that may be a
good thing to do in the short-term.
But only if we won't add any more like "checkout-index --prefix". If you
want to implement "git checkout --prefix=over-there/" and if you want to
call check_path() directly (iow not as a part of callchain from
checkout_entry()) while doing so, for example, you would regret keeping
the check_path() function unaware of base_dir, as you would reintroduce
the same bug.
I thought about getting rid of base_dir from struct checkout by running
create_directories() in checkout-index and chdir(2) there, because this is
a very special case codepath anyway. I actually haven't tried it, but it
probably will have bad interactions with the way we find $GIT_DIR.
prev parent reply other threads:[~2009-08-17 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 1:16 "make quick-install-man" broke recently Randal L. Schwartz
2009-08-17 1:29 ` Junio C Hamano
2009-08-17 1:33 ` Randal L. Schwartz
2009-08-17 5:17 ` Junio C Hamano
2009-08-17 5:58 ` Jacob Helwig
2009-08-17 6:01 ` Randal L. Schwartz
2009-08-17 6:53 ` Junio C Hamano
2009-08-17 8:00 ` Johannes Sixt
2009-08-17 8:02 ` Junio C Hamano
2009-08-17 14:26 ` Randal L. Schwartz
2009-08-17 15:57 ` Junio C Hamano
2009-08-17 16:34 ` Linus Torvalds
2009-08-17 17:09 ` 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=7vhbw6weo9.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barvik@broadpark.no \
--cc=git@vger.kernel.org \
--cc=jacob.helwig@gmail.com \
--cc=merlyn@stonehenge.com \
--cc=torvalds@linux-foundation.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