emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: local.mk and SUDO
Date: Fri, 27 Apr 2012 20:11:34 +0200	[thread overview]
Message-ID: <87r4v9vycp.fsf@Rainer.invalid> (raw)
In-Reply-To: m2sjfps66z.fsf@btinternet.com

Martyn Jago writes:
> However, when I've just gone to run `make up2' (awesome command by the
> way), I get the error:
> diff --git a/lisp/org-mobile.el b/lisp/org-mobile.el
> old mode 100644
> new mode 100755

That's a well-known problem with anything that expects POSIX file
semantics on Windows... and Git does rely very heavily on it.

> After further investigation, I have modified git config to overide the
> core.filemode setting which works for me:
> git config core.filemode false

You should preferrably set it before any commits to that repo (or rather
in global config).  Otherwise you could use Git from Cygwin (which
emulates POSIX on anything but FAT by default), but then you must never
use any native Git on that repo (and be sure that you never access it
via a filesystem that doesn't have ACL or that is mounted with "noacl"
in Cygwin).  This particular pitfall is extensively documented on the
Git side.

> So really - this is just a heads-up of my experience setting SUDO to
> blank, but it would be nice to know if this is expected behavior? If it
> turns out that it is, then perhaps I can supply a documentation patch
> (an extra comment in default.mk).

I'm not sure that orgmode should document limitations of some other
software that are caused be the underlying OS...

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:

  reply	other threads:[~2012-04-27 18:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 12:35 local.mk and SUDO Martyn Jago
2012-04-27 18:11 ` Achim Gratz [this message]
2012-04-27 20:02   ` Martyn Jago
2012-04-27 22:57     ` Achim Gratz
2012-04-29 12:59       ` Martyn Jago
2012-04-29 21:57         ` Achim Gratz

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87r4v9vycp.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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