From: Greg Troxel <gdt@ir.bbn.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: makefile regression
Date: Thu, 24 May 2012 20:12:59 -0400 [thread overview]
Message-ID: <rmi7gw12k50.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: 87wr41ebzw.fsf@Rainer.invalid
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
Achim Gratz <Stromeko@nexgo.de> writes:
> Could you please state clearly what you want to have changed and
> possibly how? You keep wandering back and forth in your arguments, but
What I meant was:
If GNU make is required it needs to be documented.
Separately from that, the makefiles look much more complicated than I
would have thought necessary, and if there aren't good reasons to
require more than POSIX make, it would be nice to stay with POSIX.
> to me it seems simply adding a sentence or two to the README file about
> the need for GNU make would suffice until the full documentation is
> finished. I'm sure Bastien would appreciate if you could supply a patch
> for it.
Fair enough - I have sent a patch which adds to the README the kind of
information present in almost all other software pacakges. It needs
adjusting to list the XEmacs versions that org can use, but I think it's
close.
Thanks,
Greg
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2012-05-25 0:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 14:43 makefile regression Greg Troxel
2012-05-22 16:20 ` Bastien
2012-05-24 6:00 ` Achim Gratz
2012-05-24 9:05 ` Bastien
2012-05-24 12:12 ` Greg Troxel
2012-05-24 17:15 ` Achim Gratz
2012-05-25 0:08 ` [PATCH] Add section describing prerequisites Greg Troxel
2012-05-25 22:33 ` Bastien
2012-05-25 23:52 ` Greg Troxel
2012-05-25 0:12 ` Greg Troxel [this message]
2012-05-25 18:43 ` makefile regression 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=rmi7gw12k50.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@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/org-mode.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).