From: "Óscar Fuentes" <ofv@wanadoo.es>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: Incorrect merge
Date: Wed, 03 Nov 2010 07:46:06 +0100 [thread overview]
Message-ID: <87oca6hpld.fsf@telefonica.net> (raw)
In-Reply-To: <871v73c775.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Wed, 03 Nov 2010 14:22:22 +0900")
"Stephen J. Turnbull" <stephen@xemacs.org> writes:
[snip]
> Your way requires all committers who fix bugs to worry about which
> branch to commit to.
Yes, exactly as it happens right now.
Maybe you didn't notice that people commit to emacs-23 (and to emacs-23
only) whenever the fix applies to that release, and to trunk only
otherwise. Then, from time to time, some maintainer merges (or, more
precisely, cherry picks) emacs-23 into trunk. This means that people
already need to figure out where to commit their fixes. Replacing
emacs-23 with common-fixes here seems a tiny change on the workflow to
me, much less burdensome than waiting for the availability and using a
script that fakes cherry-pick tracking on bzr.
(Good luck writing that script. It looks much harder to do than on the
svn case, if possible at all without extending the repository format.)
next prev parent reply other threads:[~2010-11-03 6:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 13:48 Incorrect merge Ken Brown
2010-11-01 15:46 ` 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 [this message]
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=87oca6hpld.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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 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).