From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: dmantipov@yandex.ru, monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r109327: Generalize INTERNAL_FIELD between buffers, keyboards and frames.
Date: Thu, 02 Aug 2012 18:45:10 +0300 [thread overview]
Message-ID: <83ehnpcn7d.fsf@gnu.org> (raw)
In-Reply-To: <87a9ydbzwf.fsf@uwakimon.sk.tsukuba.ac.jp>
> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Date: Thu, 02 Aug 2012 14:56:16 +0900
> Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, emacs-devel@gnu.org
>
> For you personally, why don't you talk to Miles (aka Mr. Lexbind) and
> Eli (aka Mr. BIDI) and see if they have some hints for maintaining
> one's own enthusiasm for working on a long-lived branch?
My experience with this is that merging is not a problem at all. I
just grepp'ed my .bzr.log files for the 2 years I developed bidi on a
branch, and found only 11 conflicts there. Given that I was merging
from the trunk once a week, this number is all but negligible.
To be fair, I was mainly hacking a single source file (and another one
that didn't exist on the trunk, so it doesn't count). But the same is
probably true for GC-related work: it mainly affects alloc.c, and
that's it.
So, all in all, I don't understand what's all the fuss about merging
nightmare. For me, one of the main advantages of bzr (which is common
to all modern dVCSes) is the much smarter merging, with the result
that conflicts are almost non-existent. I used to be petrified by
merges and branches when I used CVS; now I don't think twice when I
need to make a branch and work on it for a while.
Just try it.
next prev parent reply other threads:[~2012-08-02 15:45 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1SwCK8-0001PC-3m@vcs.savannah.gnu.org>
2012-08-01 10:33 ` [Emacs-diffs] /srv/bzr/emacs/trunk r109327: Generalize INTERNAL_FIELD between buffers, keyboards and frames Stefan Monnier
2012-08-01 12:04 ` Dmitry Antipov
2012-08-01 14:58 ` Paul Eggert
2012-08-01 16:52 ` Dmitry Antipov
2012-08-01 17:38 ` Tom Tromey
2012-08-01 21:04 ` Paul Eggert
2012-08-02 5:28 ` Stephen J. Turnbull
2012-08-01 15:01 ` Eli Zaretskii
2012-08-01 18:02 ` Dmitry Antipov
2012-08-02 15:28 ` Eli Zaretskii
2012-08-01 23:52 ` Stefan Monnier
2012-08-02 4:12 ` Dmitry Antipov
2012-08-02 5:56 ` Stephen J. Turnbull
2012-08-02 7:47 ` Dmitry Antipov
2012-08-02 9:30 ` Juanma Barranquero
2012-08-02 16:07 ` Eli Zaretskii
2012-08-02 15:45 ` Eli Zaretskii [this message]
2012-08-02 21:28 ` Paul Eggert
2012-08-03 6:27 ` Eli Zaretskii
2012-08-03 6:52 ` Paul Eggert
2012-08-02 23:38 ` Richard Stallman
2012-08-02 15:34 ` Eli Zaretskii
2012-08-03 7:42 ` Stefan Monnier
2012-08-03 8:31 ` Dmitry Antipov
2012-08-03 18:58 ` Paul Eggert
2012-08-03 22:52 ` Stefan Monnier
2012-08-04 16:31 ` Paul Eggert
2012-08-05 15:03 ` Dmitry Antipov
2012-08-06 10:54 ` Stefan Monnier
2012-08-06 11:44 ` Dmitry Antipov
2012-08-06 16:31 ` Stefan Monnier
2012-08-06 17:43 ` Stefan Monnier
2012-08-08 7:22 ` Chong Yidong
2012-08-05 14:59 ` Dmitry Antipov
2012-08-05 15:23 ` Paul Eggert
2012-08-05 20:29 ` Miles Bader
2012-08-03 22:50 ` Stefan Monnier
2012-08-03 23:11 ` Wojciech Meyer
2012-08-08 3:39 ` Chong Yidong
2012-08-08 7:14 ` Dmitry Antipov
2012-08-08 7:46 ` Chong Yidong
2012-08-08 10:18 ` Dmitry Antipov
2012-08-08 12:41 ` Stefan Monnier
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=83ehnpcn7d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--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 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.