From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: Emacs 23.2 released
Date: Sat, 08 May 2010 14:57:54 -0400 [thread overview]
Message-ID: <jwvk4regrhd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83632yqqmy.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 08 May 2010 19:56:05 +0300")
>> But feel free to revise your commits to the trunk and see if any of them
>> might be good candidates for Emacs-23.3.
> What is the recommended bzr procedure for backporting changes from the
> trunk, without introducing possible conflicts in future merges from
> the branch to the trunk?
I don't think there's any magic bullet, sadly. Until now, I've been the
one who did the merges, so it basically means more pain for me.
One thing you can do to help me out is to label your backports as such,
by starting the commit message with "Backport:". It won't make all
problems disappear, but it gives me a few more options for how to deal
with them (e.g.: merge up to the next non-backport, commit, then
merge the next backport(s), "bzr revert .", commit, ...;
this work particularly well if the backport-commits are contiguous).
Stefan
next prev parent reply other threads:[~2010-05-08 18:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 5:29 Emacs 23.2 released Chong Yidong
2010-05-08 12:56 ` Drew Adams
2010-05-08 13:56 ` Sean Sieger
2010-05-08 14:00 ` Drew Adams
[not found] ` <mailman.5.1273327224.12744.help-gnu-emacs@gnu.org>
2010-05-08 20:56 ` Alex Schroeder
2010-05-08 21:48 ` Juanma Barranquero
2010-05-09 3:35 ` Stefan Monnier
[not found] ` <mailman.1.1273355333.21825.help-gnu-emacs@gnu.org>
2010-05-09 9:00 ` Alex Schroeder
2010-05-08 16:46 ` Stefan Monnier
2010-05-08 16:56 ` Eli Zaretskii
2010-05-08 18:57 ` Stefan Monnier [this message]
2010-05-09 11:19 ` Neal Becker
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=jwvk4regrhd.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=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.