From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: git:
Date: Sat, 28 Feb 2015 00:10:36 +0100 [thread overview]
Message-ID: <87mw3zgdcj.fsf@web.de> (raw)
In-Reply-To: 20150226222407.GA18239@boo.workgroup
Gregor Zattler <telegraph@gmx.net> writes:
> Any idea why this happens and what to do aginst this?
The Rmail sources seem to use rmail.el as source file and autoloads file
at the same time.
Obviously that's the cause why rmail.el is touched when compiling.
The hash in the diff is an md5 checksum generated by
`autoload-generate-file-autoloads'. I'm not sure why the md5 hashes
differ, but this happened to me too.
I suggest to make a bug report please - this is more than confusing.
Thanks,
Michael.
next prev parent reply other threads:[~2015-02-27 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 22:24 git: Gregor Zattler
2015-02-27 15:08 ` git: J. David Boyd
2015-02-28 0:03 ` git: Bob Proulx
2015-02-27 23:10 ` Michael Heerdegen [this message]
2015-02-27 23:57 ` git: Gregor Zattler
2015-02-28 0:24 ` git: Glenn Morris
2015-02-28 0:30 ` git: Glenn Morris
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mw3zgdcj.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@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.
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).