From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: ofv@wanadoo.es, Alan Mackenzie <acm@muc.de>,
Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: [PATCH] support a few of the new features of C++11 in syntax highlighting
Date: Sat, 17 May 2014 10:14:37 -0400 [thread overview]
Message-ID: <jwv1tvsmr7z.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87mwegzii1.fsf@gmx.de> (Michael Albinus's message of "Sat, 17 May 2014 14:39:50 +0200")
> Technically spoken, you're right. But it might be difficult to request
> from an XEmacs user to checkout code from the GNU Emacs repository in
> order to test the very recent patches.
The issue is not whether there's an external repository. The issue is
about having a separate branch that evolves separately such that it ends
up drifting apart.
Gnus is a good example: they have an external branch (or even several),
but that external branch and the code in Emacs are constantly kept in
sync, so they don't need to worry about finding an Óscar to port some
new feature to the other branch: they can ask "git/bzr merge" to do that
job instead.
Stefan
next prev parent reply other threads:[~2014-05-17 14:14 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 12:51 [PATCH] support a few of the new features of C++11 in syntax highlighting Paul Pogonyshev
2014-01-25 19:58 ` Glenn Morris
2014-01-25 21:56 ` Stefan Monnier
2014-01-25 22:34 ` Daniel Colascione
2014-01-26 0:27 ` Glenn Morris
2014-01-26 12:29 ` Daniel Colascione
2014-01-26 15:21 ` Alan Mackenzie
2014-05-11 6:48 ` Václav Zeman
2014-05-11 16:00 ` Óscar Fuentes
2014-05-11 18:21 ` Glenn Morris
2014-05-11 20:19 ` Óscar Fuentes
2014-05-11 22:09 ` Alan Mackenzie
2014-05-11 22:38 ` Óscar Fuentes
2014-05-14 20:13 ` Alan Mackenzie
2014-05-14 21:20 ` Óscar Fuentes
2014-05-15 1:52 ` Stefan Monnier
2014-05-16 16:07 ` Alan Mackenzie
2014-05-16 17:59 ` Eli Zaretskii
2014-05-17 8:31 ` Alan Mackenzie
2014-05-17 9:24 ` Eli Zaretskii
2014-05-17 12:39 ` Michael Albinus
2014-05-17 14:14 ` Stefan Monnier [this message]
2014-05-17 14:24 ` Michael Albinus
2014-05-17 15:10 ` Stefan Monnier
2014-05-17 13:27 ` Óscar Fuentes
2014-05-17 14:06 ` Eli Zaretskii
2014-05-16 23:42 ` Stefan Monnier
2014-05-17 4:17 ` Richard Stallman
2014-05-17 9:03 ` Alan Mackenzie
2014-05-17 15:45 ` Richard Stallman
2014-05-19 15:46 ` Barry Warsaw
2014-05-17 8:42 ` Alan Mackenzie
2014-05-17 14:09 ` Stefan Monnier
2014-11-16 17:36 ` Rüdiger Sonderfeld
2014-11-16 18:07 ` Óscar Fuentes
2014-11-18 2:41 ` Rüdiger Sonderfeld
2014-11-18 3:30 ` Óscar Fuentes
2014-11-18 12:48 ` Daniel Colascione
2014-11-18 14:47 ` Óscar Fuentes
2014-11-18 16:36 ` Rüdiger Sonderfeld
2014-11-18 17:13 ` Daniel Colascione
2014-11-18 18:01 ` Óscar Fuentes
2014-11-18 18:11 ` Daniel Colascione
2014-11-18 18:33 ` Óscar Fuentes
2014-11-18 12:49 ` Daniel Colascione
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=jwv1tvsmr7z.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=ofv@wanadoo.es \
/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).