From: Dmitry Gutov <dgutov@yandex.ru>
To: emacs-devel@gnu.org
Subject: Re: status of ruby-mode.el
Date: Sun, 01 Apr 2012 08:52:19 +0400 [thread overview]
Message-ID: <87obrc3vgc.fsf@yandex.ru> (raw)
In-Reply-To: jwv62dw4jvp.fsf-monnier+emacs@gnu.org
Hi Stefan,
>> I found this message on the ruby mailing-list which suggests development
>> was supposed to move to Emacs, but the Ruby's HEAD version of ruby-mode.el
>> clearly has further changes.
>
> Damn! Could someone take care of this problem (.i.e. merge their
> changes into our trunk and then try to make it won't happen again)?
I can prepare a patch (or several) with unmerged changes from upstream,
if that will help, but how would one go about the latter part?
Did you mean just keep an eye on them?
-- Dmitry
prev parent reply other threads:[~2012-04-01 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 14:58 status of ruby-mode.el Le Wang
2012-03-22 16:36 ` Dmitry Gutov
2012-03-22 17:38 ` Stefan Monnier
2012-04-01 4:52 ` Dmitry Gutov [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=87obrc3vgc.fsf@yandex.ru \
--to=dgutov@yandex.ru \
--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 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).