From: Eli Zaretskii <eliz@gnu.org>
To: Leo <sdl.web@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Move sha1 to C?
Date: Mon, 23 May 2011 10:30:13 -0400 [thread overview]
Message-ID: <E1QOW97-0005Ty-7x@fencepost.gnu.org> (raw)
In-Reply-To: <m1d3j97d6u.fsf@th041094.ip.tsinghua.edu.cn> (message from Leo on Mon, 23 May 2011 21:34:49 +0800)
> From: Leo <sdl.web@gmail.com>
> Date: Mon, 23 May 2011 21:34:49 +0800
> Cc: emacs-devel@gnu.org
>
> edited Makefile.in
> lib/
> * edited lib/gnulib.mk
> * unregistered lib/sha1.c
> * unregistered lib/sha1.h
> * edited lib/verify.h
> lisp/
> edited lisp/bindings.el
> removed lisp/sha1.el
> lisp/vc/
> edited lisp/vc/vc-bzr.el
> edited lisp/vc/vc.el
> m4/
> * edited m4/gl-comp.m4
> * unregistered m4/sha1.m4
> src/
> edited src/deps.mk
> edited src/fns.c
Don't you need to modify lib/Makefile.am as well?
Btw, if you can afford it, please consider making in
src/makefile.w32-in and in lib/makefile.w32-in the changes equivalent
to what you did in src/deps.mk and lib/gnulib.mk, respectively, to
prevent the Windows build from breaking. TIA.
next prev parent reply other threads:[~2011-05-23 14:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 6:37 Move sha1 to C? Leo
2011-05-22 19:04 ` Stefan Monnier
2011-05-22 20:02 ` Leo
2011-05-23 1:23 ` Stefan Monnier
2011-05-23 8:44 ` Leo
2011-05-23 12:04 ` Stefan Monnier
2011-05-23 13:21 ` Leo
2011-05-23 13:27 ` Stefan Monnier
2011-05-23 13:34 ` Leo
2011-05-23 13:57 ` Stefan Monnier
2011-05-23 18:14 ` Leo
2011-05-23 19:15 ` Stefan Monnier
2011-05-23 22:10 ` Paul Eggert
2011-05-24 4:09 ` Leo
2011-05-24 10:01 ` Eli Zaretskii
2011-05-24 14:24 ` Leo
2011-05-24 22:01 ` Richard Stallman
2011-05-24 5:09 ` Thien-Thi Nguyen
2011-05-23 14:30 ` Eli Zaretskii [this message]
2011-05-23 17:47 ` Leo
2011-05-23 18:12 ` Eli Zaretskii
2011-05-23 18:23 ` Leo
2011-05-23 19:21 ` Eli Zaretskii
2011-05-23 7:21 ` Eli Zaretskii
2011-05-23 8:30 ` Leo
2011-05-23 15:27 ` Chong Yidong
2011-05-23 17:14 ` Leo
2011-05-23 17:38 ` Leo
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=E1QOW97-0005Ty-7x@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=sdl.web@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.