unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@floss.red-bean.com>
Cc: belanger@truman.edu, emacs-devel@gnu.org
Subject: Re: Please check-in Belanger's Calc patches
Date: 13 Jul 2004 12:42:24 -0500	[thread overview]
Message-ID: <87fz7vls73.fsf@floss.red-bean.com> (raw)
In-Reply-To: <BAY15-DAV79Etm7mCuW000cdd25@hotmail.com>

"Tacvek" <unknown_kev_cat@hotmail.com> writes:
> Perhaps the emacs developers are slow, but i find it unreasonable that a bug
> with a patch approved by a compenents maintainer has been waiting 3/4 of a
> year before getting checked in. Yet this is the case with Belanger's Calc
> patches. they were approved by the Calc maintainer
> (http://lists.gnu.org/archive/html/emacs-devel/2003-10/msg00719.html), and
> posted to the list twice, the second time by an indirect request from RMS
> himself
> (http://lists.gnu.org/archive/html/emacs-devel/2004-02/msg00437.html).
> 
> I believe the patches may now be slightly out of date, so can you remake
> them against the current cvs, Belanger?
> 
> I ask that this problem be fixed, and included in the next minor release.

I might be missing some background here, but is there some reason the
Calc maintainer can't commit these changes?  When patches are approved
by the component maintainer, then normally the maintainer just checks
them in.

IOW, why is this situation special?

Thanks,
-Karl

  reply	other threads:[~2004-07-13 17:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 16:09 Please check-in Belanger's Calc patches Tacvek
2004-07-13 17:42 ` Karl Fogel [this message]
2004-07-14  3:40 ` Jay Belanger
2004-07-14 18:27 ` Richard Stallman
2004-07-14 16:00   ` Karl Fogel
2004-07-20 17:40     ` Karl Fogel
2004-07-21 14:07       ` Stefan
2004-07-21 14:59         ` Jay Belanger
2004-07-21 15:44           ` Stefan Monnier
2004-07-21 17:16             ` Jay Belanger
2004-07-21 17:42               ` Jay Belanger

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=87fz7vls73.fsf@floss.red-bean.com \
    --to=kfogel@floss.red-bean.com \
    --cc=belanger@truman.edu \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.com \
    /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).