From: joakim@verona.se
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r101135: merge the imagemagick branch to trunk
Date: Thu, 19 Aug 2010 14:28:40 +0200 [thread overview]
Message-ID: <m362z6wzuv.fsf@verona.se> (raw)
In-Reply-To: <AANLkTim56Vp+OEtUzE_k_f7judqG8ynMVs9KH3+_mxcG@mail.gmail.com> (Juanma Barranquero's message of "Thu, 19 Aug 2010 14:04:04 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
> A few nitpicks (not related to code, just the merge).
>
> On Thu, Aug 19, 2010 at 09:35, Joakim <joakim@localhost.localdomain> wrote:
>
>> modified:
>> ChangeLog
>
> There's just a ChangeLog entry, at top level, but the changes should
> be documented in the respective ChangeLogs (src/ChangeLog for src/*
> changes, etc.).
>
>> configure
>> doc/lispref/display.texi
>> etc/NEWS
>> lisp/image-mode.el
>
> These aren't mentioned in any ChangeLog.
>
>> +2010-06-12 Joakim Verona <joakim@verona.se>
>
> When merging branches, the date of the ChangeLog is the date the merge
> is done, not that of the original changes (that information is
> preserved by the branch history).
>
>> + * image.c: Add support for ImageMagick. When HAVE_IMAGEMAGICK is
>> + defined:
>
> Usually that information is conveyed by "[HAVE_IMAGEMAGICK]".
>
>> + * config.in, Makefile.in, configure.in
>
> These files do not have a change description in the entry.
Ok, Ill try to fix these issues.
> Juanma
>
--
next prev parent reply other threads:[~2010-08-19 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Om0JS-0000km-Hv@internal.in.savannah.gnu.org>
2010-08-19 12:04 ` [Emacs-diffs] /srv/bzr/emacs/trunk r101135: merge the imagemagick branch to trunk Juanma Barranquero
2010-08-19 12:28 ` joakim [this message]
2010-08-19 14:34 ` Stefan Monnier
2010-08-20 2:05 ` Katsumi Yamaoka
2010-08-20 5:56 ` Katsumi Yamaoka
2010-08-20 8:58 ` Eli Zaretskii
2010-08-20 10:43 ` joakim
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=m362z6wzuv.fsf@verona.se \
--to=joakim@verona.se \
--cc=emacs-devel@gnu.org \
--cc=lekktu@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.