From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: OS X (configure --with-ns) typing unresponsive with Org and Viper
Date: Sat, 14 May 2016 09:59:23 -0400 [thread overview]
Message-ID: <CAM-tV--JoLFcfWoEyOWMRdFfCQqc=QJs40+8-qTe4t=PPrRV9g@mail.gmail.com> (raw)
In-Reply-To: <CALn3zoj84wkS-AtvkF_gx3xFx2Oqo1mOS0PBe-wgQKgVZF2AUg@mail.gmail.com>
On Sat, May 14, 2016 at 7:42 AM, Michael Brand
<michael.ch.brand@gmail.com> wrote:
> On Sat, May 14, 2016 at 1:31 PM, Michael Brand
> <michael.ch.brand@gmail.com> wrote:
>
>> So I thought to try building different commits but failed with current
>> master "git clone -b master git://git.sv.gnu.org/emacs.git && make
>> configure": In autogen.sh "git rev-parse --git-common-dir 2>/dev/null"
>> => "--git-common-dir" which looks wrong. My git version is 2.4.9
>> (Apple Git-60).
>
> Completing myself: Probably the "test -e .git" in autogen.ch was
> intended the other way around.
No, the intention is to find the "real" .git/ directory, in case of
building in a separate git worktree. It looks like --git-common-dir
was added only in git 2.5.0 and rev-parse just passes unrecognized
options through.
~/src/git$ git rev-parse --foo ; echo $?
--foo
0
Putting --no-flags will drop them instead, perhaps we can use that?
~/src/git$ git rev-parse --no-flags --foo --git-common-dir ; echo $?
.git
0
next prev parent reply other threads:[~2016-05-14 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 18:40 OS X (configure --with-ns) typing unresponsive with Org and Viper Michael Brand
2016-05-13 19:19 ` Paul Eggert
2016-05-14 11:31 ` Michael Brand
2016-05-14 11:42 ` Michael Brand
2016-05-14 13:59 ` Noam Postavsky [this message]
2016-05-14 17:26 ` Paul Eggert
2016-05-14 17:46 ` Michael Brand
2016-05-15 20:21 ` Michael Brand
2016-05-15 21:34 ` Paul Eggert
2016-05-16 12:22 ` Stefan Monnier
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='CAM-tV--JoLFcfWoEyOWMRdFfCQqc=QJs40+8-qTe4t=PPrRV9g@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=michael.ch.brand@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.