From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Changes to emacs-23 branch and the trunk
Date: Tue, 31 Aug 2010 20:44:20 +0900 [thread overview]
Message-ID: <tl74oeb2ei3.fsf@m17n.org> (raw)
In-Reply-To: <jwvtymbi3d5.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 31 Aug 2010 10:43:18 +0200)
In article <jwvtymbi3d5.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> > So to apply your procedure in the above model, what I should
> > do is this, right?
> > A % cd work-23
> > <make-change>
> > % bzr commit -m 'my change'
> > % cd ../emacs-23
> > B % bzr up
> > <assuming that there's no new change>
> > C % bzr merge ../work-23
> > % bzr commit -m 'my change'
> > % cd ../work
> > % bzr merge ../emacs-23
> > <fix conflicts>
> > % bzr commit -m "Merge by hand from emacs-23"
> > % cd ../trunk
> > % bzr up
> > <assuming that there's no new change>
> > % bzr commit -m "Merge by hand from emacs-23"
> That looks right, yes, except for a missing "bzr merge ../work" before
> the last commit.
Ah, sure, I forgot to write that step.
But, I've just proceeded to "% bzr merge ../emacs-23", and
this message was shown:
[work] bzr merge ../emacs-23
M doc/man/ChangeLog
M doc/man/emacs.1
M doc/misc/ChangeLog
M etc/ChangeLog
M etc/emacs3.py
M leim/ChangeLog
M leim/quail/japanese.el
M lisp/ChangeLog
M lisp/disp-table.el
M lisp/international/mule-cmds.el
M lisp/net/rcirc.el
M lisp/net/tramp-cmds.el
M lisp/net/tramp-compat.el
M lisp/net/tramp-fish.el
M lisp/net/tramp-ftp.el
M lisp/net/tramp-gvfs.el
M lisp/net/tramp-imap.el
M lisp/net/tramp-smb.el
M lisp/net/tramp-uu.el
M lisp/net/trampver.el
M lisp/play/cookie1.el
M lisp/progmodes/python.el
M lisp/simple.el
M src/ChangeLog
M src/dispextern.h
M src/term.c
M src/xdisp.c
Text conflict in doc/misc/ChangeLog
Text conflict in etc/ChangeLog
Text conflict in lisp/ChangeLog
Text conflict in lisp/net/rcirc.el
Text conflict in src/ChangeLog
Text conflict in src/xdisp.c
6 conflicts encountered.
This is strange. The above step apparently merged more than
what I committed in emacs-23 branch. That commit was done
as this just before the above merge:
[emacs-23] bzr commit -m 'Fix handling of 8-bit characters in a display table.'
Committing to: sftp://bzr.savannah.gnu.org/srv/bzr/emacs/emacs-23/
modified lisp/ChangeLog
modified lisp/disp-table.el
modified lisp/international/mule-cmds.el
modified src/ChangeLog
modified src/dispextern.h
modified src/term.c
modified src/xdisp.c
Committed revision 100011.
What was wrong?
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2010-08-31 11:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 8:20 Changes to emacs-23 branch and the trunk Kenichi Handa
2010-08-30 14:19 ` Chong Yidong
2010-08-30 20:20 ` Juanma Barranquero
2010-09-14 15:03 ` Juanma Barranquero
2010-09-16 22:33 ` Chong Yidong
2010-09-17 15:09 ` Juanma Barranquero
2010-08-30 16:03 ` Stefan Monnier
2010-08-31 1:54 ` Kenichi Handa
2010-08-31 8:43 ` Stefan Monnier
2010-08-31 11:44 ` Kenichi Handa [this message]
2010-08-31 11:59 ` Andreas Schwab
2010-08-31 12:37 ` Kenichi Handa
2010-08-31 17:05 ` Eli Zaretskii
2010-08-31 13:08 ` Stefan Monnier
2010-09-01 0:32 ` Kenichi Handa
2010-09-01 7:01 ` Stefan Monnier
2010-09-02 2:49 ` Kenichi Handa
2010-09-02 5:07 ` Eli Zaretskii
2010-09-02 5:33 ` Kenichi Handa
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=tl74oeb2ei3.fsf@m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).