unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Emacs <emacs-devel@gnu.org>
Subject: Incorrect merge
Date: Mon, 01 Nov 2010 09:48:22 -0400	[thread overview]
Message-ID: <4CCEC526.3070502@cornell.edu> (raw)

Hi Michael,

It looks like the following change got merged with the trunk inadvertently:

revno: 100136
committer: Michael Albinus <michael.albinus@gmx.de>
branch nick: emacs-23
timestamp: Mon 2010-10-25 13:46:21 +0200
message:
   * dbusbind.c (Fdbus_call_method_asynchronously)
   (Fdbus_register_signal, Fdbus_register_method): Check, whether
   `dbus-registered-objects-table' is initialized.

   Must not be synchronized with the trunk.

Ken



             reply	other threads:[~2010-11-01 13:48 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 13:48 Ken Brown [this message]
2010-11-01 15:46 ` Incorrect merge Chong Yidong
2010-11-01 16:02 ` Chong Yidong
2010-11-01 17:54   ` Eli Zaretskii
2010-11-01 20:21     ` Juanma Barranquero
2010-11-01 20:37       ` Eli Zaretskii
2010-11-01 22:19         ` Juanma Barranquero
2010-11-02  1:50           ` Stephen J. Turnbull
2010-11-02 14:54             ` Stefan Monnier
2010-11-02 15:57               ` Óscar Fuentes
2010-11-02 16:45                 ` Stephen J. Turnbull
2010-11-02 17:14                   ` Óscar Fuentes
2010-11-02 18:34                     ` Stephen J. Turnbull
2010-11-02 18:56                       ` Óscar Fuentes
2010-11-02 20:25                         ` Stephen J. Turnbull
2010-11-02 20:44                           ` Óscar Fuentes
2010-11-03  5:22                             ` Stephen J. Turnbull
2010-11-03  6:46                               ` Óscar Fuentes
2010-11-03  7:44                                 ` Stephen J. Turnbull
2010-11-03 13:51                                   ` Stefan Monnier
2010-11-04 20:16                                     ` Lars Magne Ingebrigtsen
2010-11-05  9:30                                       ` Andreas Schwab
2010-11-05 11:42                                         ` Eli Zaretskii
2010-11-08 16:03                                       ` Stefan Monnier
2010-11-03  6:52                               ` Óscar Fuentes
2010-11-03  7:47                                 ` Stephen J. Turnbull
2010-11-02 17:22                 ` Stefan Monnier
2010-11-02 17:37                   ` Óscar Fuentes
2010-11-02 18:38                 ` Eli Zaretskii
2010-11-02 19:19                   ` Óscar Fuentes
2010-11-02 21:21                     ` Stefan Monnier
2010-11-01 23:02         ` Óscar Fuentes
2010-11-02  1:29           ` Jason Rumney
2010-11-02  5:16             ` Óscar Fuentes
2010-11-02  9:16               ` Andreas Schwab
2010-11-02 14:17                 ` Óscar Fuentes
2010-11-02 17:24                   ` Stefan Monnier
2010-11-02 17:41                     ` Óscar Fuentes
2010-11-02 17:44                     ` Davis Herring

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=4CCEC526.3070502@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.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).