unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sds@gnu.org, Emacs-devel@gnu.org, eggert@cs.ucla.edu
Subject: Re: make bootstrap fails: cp: .git/hooks/applypatch-msg.sample: No	such file or directory
Date: Tue, 27 Jan 2015 19:07:18 +0100	[thread overview]
Message-ID: <0D82442F-A5DE-49A7-A536-D92441910007@swipnet.se> (raw)
In-Reply-To: <83ppa0p1h2.fsf@gnu.org>

Hi.

> 27 jan 2015 kl. 18:39 skrev Eli Zaretskii <eliz@gnu.org>:
> 
>> Date: Tue, 27 Jan 2015 10:11:52 +0100
>> From: "Jan D." <jan.h.d@swipnet.se>
>> Cc: Emacs Development <Emacs-devel@gnu.org>
>> 
>> Paul Eggert skrev den 2015-01-27 07:50:
>>> Sam Steingold wrote:
>>> 
>>>> .$ mkcd z
>>>> ./z [37]$ git init
>>>> Initialized empty Git repository in ./z/.git/
>>>> ./z [38]$ ls -R .git/
>>>> ...
>>>> .git//hooks:
>>>> total 40
>>>> 8 ctags*        8 post-checkout*    8 post-commit*        8
>>>> post-merge*        8 post-rewrite*
>>> 
>>> That's odd.  It doesn't look like my .git/hooks at all.  I wonder what
>>> other incompatibility bombs Apple has planted in their version of Git?
>> 
>> FWIW, no git repository I have on OSX (2 machines about 20 repositories) 
>> has this layout.  This is what they have:
>> 
>> % ls .git/hooks/
>> applypatch-msg.sample*     pre-push.sample*
>> commit-msg.sample*         pre-rebase.sample*
>> post-update.sample*        prepare-commit-msg.sample*
>> pre-applypatch.sample*     update.sample*
>> pre-commit.sample*
>> 
>> % git --version
>> git version 1.9.3 (Apple Git-50)
>> 
>> I think this is a local problem, not a general one.
> 
> It's beginning to sound like one.
> 
> So maybe something happened to /usr/share/git-core/templates/hooks
> directory (or wherever it is on OS X) on Sam's machine.  What do you
> (Sam) see there?

/Applications/Xcode.app//Contents/Developer/usr/share/git-core/templates/hooks

	Jan D.

> 
> Or maybe Sam has an alias that calls "git init" with --template
> option, pointing it to  a non-standard place.  (What does
> "git config -l" display?)
> 
> Or maybe GIT_TEMPLATE_DIR is set in the environment on Sam's machine.
> 
> Or something similar.




  reply	other threads:[~2015-01-27 18:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 16:48 make bootstrap fails: cp: .git/hooks/applypatch-msg.sample: No such file or directory Sam Steingold
2015-01-26 19:31 ` Paul Eggert
2015-01-27  2:25   ` Sam Steingold
2015-01-27  5:37     ` Paul Eggert
2015-01-27  5:46       ` Sam Steingold
2015-01-27  6:50         ` Paul Eggert
2015-01-27  7:57           ` chad
2015-01-27  9:11           ` Jan D.
2015-01-27 17:39             ` Eli Zaretskii
2015-01-27 18:07               ` Jan D. [this message]
2015-01-27 20:59                 ` Sam Steingold
2015-01-27 21:09               ` Sam Steingold
2015-01-27 22:44                 ` Paul Eggert
2015-01-27 17:53           ` Sam Steingold

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0D82442F-A5DE-49A7-A536-D92441910007@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=Emacs-devel@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=sds@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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