From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Merging mistakes
Date: Sat, 04 Dec 2010 11:35:56 +0200 [thread overview]
Message-ID: <8362v998xv.fsf@gnu.org> (raw)
The kind of problems described below happens too much lately. I think
the unbearable lightness of merging with Bazaar is at least one of the
reasons. Unless we find a safer way of doing this, I fear that Emacs
23.3 will either take a very long pretesting or will be released more
buggy than Emacs 23.2.
Any suggestions for how to avoid destabilizing the release branch by
too indiscriminate back-ports from the trunk?
------- Start of forwarded message -------
Resent-From: Sven Joachim <svenjoac@gmx.de>
Original-Sender: debbugs-submit-bounces@debbugs.gnu.org
Resent-To: owner@debbugs.gnu.org
Resent-CC: svenjoac@gmx.de, bug-gnu-emacs@gnu.org
Resent-Sender: help-debbugs@gnu.org
To: 7539@debbugs.gnu.org
From: Sven Joachim <svenjoac@gmx.de>
Date: Fri, 03 Dec 2010 11:15:15 +0100
Cc: Sven Joachim <svenjoac@gmx.de>
Subject: bug#7539: 23.2.90; smie.el uses stuff not available in emacs-23
Byte-compiling lisp/emacs-lisp/smie.el in emacs-23 gives the following
warnings:
,----
| In smie-setup:
| smie.el:1536:14:Warning: assignment to free variable
| `blink-matching-check-function'
|
| In end of data:
| smie.el:1559:1:Warning: the function `blink-matching-check-mismatch' is not
| known to be defined.
`----
Indeed blink-matching-check-function and blink-matching-check-mismatch
only exist in the trunk, not in emacs-23.
------- End of forwarded message -------
next reply other threads:[~2010-12-04 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 9:35 Eli Zaretskii [this message]
2010-12-04 14:00 ` Merging mistakes Stefan Monnier
2010-12-04 14:42 ` Leo
2010-12-04 16:14 ` Stefan Monnier
2010-12-04 16:34 ` Leo
2010-12-04 15:18 ` Eli Zaretskii
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=8362v998xv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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.
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.