From: Xavier Maillard <zedek@gnu.org>
To: git@vger.kernel.org
Subject: [PATCH] Use non-interactive function to byte-compile files
Date: Mon, 5 Mar 2007 09:23:42 +0100 [thread overview]
Message-ID: <200703050823.l258NgT9008266@localhost.localdomain> (raw)
Hi,
Ihope this one is more closed to what you expect to see in a
commit log.
* contrib/emacs/Makefile: add git-blame as a candidate to the
byte-compilation. batch-byte-compile is the prefered way
to byte-compile files in batch mode. Use it instead of the
interactive function.
Signed-off-by: Xavier Maillard <zedek@gnu.org>
---
contrib/emacs/Makefile | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/contrib/emacs/Makefile b/contrib/emacs/Makefile
index 350846d..8554e39 100644
--- a/contrib/emacs/Makefile
+++ b/contrib/emacs/Makefile
@@ -2,7 +2,7 @@
EMACS = emacs
-ELC = git.elc vc-git.elc
+ELC = git.elc vc-git.elc git-blame.elc
INSTALL ?= install
INSTALL_ELC = $(INSTALL) -m 644
prefix ?= $(HOME)
@@ -15,6 +15,6 @@ install: all
$(INSTALL_ELC) $(ELC) $(emacsdir)
%.elc: %.el
- $(EMACS) --batch --eval '(byte-compile-file "$<")'
+ $(EMACS) -batch -f batch-byte-compile $<
clean:; rm -f $(ELC)
--
1.5.0
next reply other threads:[~2007-03-05 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 8:23 Xavier Maillard [this message]
2007-03-05 9:51 ` [PATCH] Use non-interactive function to byte-compile files Karl Hasselström
2007-03-05 14:54 ` Johannes Schindelin
2007-03-05 15:04 ` Karl Hasselström
2007-03-05 15:37 ` [PATCH] Begin SubmittingPatches with a check list Johannes Schindelin
2007-03-05 17:28 ` Alex Riesen
2007-03-05 20:52 ` Brian Gernhardt
2007-03-05 23:14 ` Johannes Schindelin
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=200703050823.l258NgT9008266@localhost.localdomain \
--to=zedek@gnu.org \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).