unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: JD Smith <jdtsmith@gmail.com>, emacs-devel@gnu.org
Subject: Re: Updating idlwave in Emacs
Date: Fri, 18 Jul 2014 11:36:42 -0400	[thread overview]
Message-ID: <jwvlhrqheeg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <1f7g3enqro.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 15 Jul 2014 19:31:07 -0400")

>> I am also somewhat daunted by the need to backport changes from the
>> Emacs core version of idlwave which have accumulated over the past 6
>> or so years.

Right, the problem is not so much the changes as the accumulation.
The sooner the two forks are re-merged the better.

After that, the easier way to "sync" things up is to only have one
development branch.  Having one in Emacs and one on github is asking
for trouble.

You can use the Emacs code as the main place for development, by
the way (this is up to you, but I generally recommend it).

> Although it's the more difficult job, maybe that's the place to start -
> make the definitive, merged version, then figure out where it will live?

Yes, the more we wait, the harder it gets to sync them back.


        Stefan



      reply	other threads:[~2014-07-18 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 16:27 Updating idlwave in Emacs Glenn Morris
2014-07-15 15:47 ` Glenn Morris
2014-07-15 19:12   ` JD Smith
2014-07-15 23:31     ` Glenn Morris
2014-07-18 15:36       ` Stefan Monnier [this message]

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=jwvlhrqheeg.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=jdtsmith@gmail.com \
    --cc=rgm@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 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).