From: storm@cua.dk (Kim F. Storm)
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Coordinating patches [was Re: Change in compile.el]
Date: 18 Feb 2004 13:52:04 +0100 [thread overview]
Message-ID: <m31xosy2h7.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <ufzd8zmwh.fsf@elta.co.il>
Eli Zaretskii <eliz@elta.co.il> writes:
> > From: Richard Stallman <rms@gnu.org>
> > Date: Wed, 18 Feb 2004 03:38:32 -0500
> >
> > I asked Eli to install the patches because he said he was willing to
> > do that. However, his available time has been just barely enough time
> > to do that. If I were to ask him to do this extra work for each
> > change, the most likely result is that he'd have to say no.
>
> Probably.
>
> The more I think about what I wrote earlier in this thread, the more I
> like it: if patches suggested by people other than the core
> maintainers will get reviewed and responded to by the developers soon
> after they are posted to the various lists, we will win on 2 counts:
> (1) more potential bugs will be detected before they get into the CVS,
> and (2) it will make life easier for Richard who up until now did that
> almost single-handedly.
Exactly -- if I see a new patch that I think it looks ok to include, I
can check for legal papers from poster and if ok, immediately post a
PATCH REVIEW message to emacs-devel, and in a couple of days I can
just install it if nobody has objected to do so.
No double work, no forgotten patches, no patches committed without
prior review... ?
Maybe we should say that the review period is 3 days, i.e. if no
comments in 3 days, it is ok to commit.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-02-18 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 20:08 Change in compile.el Stefan Monnier
2004-02-17 5:59 ` Eli Zaretskii
2004-02-17 10:16 ` Coordinating patches [was Re: Change in compile.el] Kim F. Storm
2004-02-17 19:43 ` Eli Zaretskii
2004-02-18 8:38 ` Richard Stallman
2004-02-18 10:45 ` Eli Zaretskii
2004-02-18 12:52 ` Kim F. Storm [this message]
2004-02-18 18:56 ` Eli Zaretskii
2004-02-18 23:38 ` Richard Stallman
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=m31xosy2h7.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=rms@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).