From: Juanma Barranquero <jmbarranquero@wke.es>
Cc: emacs-devel@gnu.org
Subject: Re: Malformed interactive spec in replace.el
Date: Tue, 06 Jul 2004 10:45:43 +0200 [thread overview]
Message-ID: <20040706104047.587A.JMBARRANQUERO@wke.es> (raw)
In-Reply-To: <x5fz85r0ri.fsf@lola.goethe.zz>
On 06 Jul 2004 10:35:45 +0200
David Kastrup <dak@gnu.org> wrote:
> That's a result of the recent disruptive changes of Stefan that were
> seemingly checked in without discussion.
I don't know about "disruptive changes". I think in this case the
problem is something trivial, like a missing `progn'.
> Could we restrict ourselves to changes that conceivably work towards
> getting into a consistent state for the release?
This is an experiment: we're now trying to see whether we can "restrict
ourselves" into working to get a release out. Perhaps we can (and more
power to us), and perhaps we cannot, and then, other models (like
branching for a release and leaving the trunk open for people who wants
to do new stuff) would be better. It's a matter of group dynamics, and
much, I think, depends on the size and cohesion of the group.
But in any case I see no point in getting angry about the outcome :)
Juanma
next prev parent reply other threads:[~2004-07-06 8:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 8:15 Malformed interactive spec in replace.el Juanma Barranquero
2004-07-06 8:35 ` David Kastrup
2004-07-06 8:45 ` Juanma Barranquero [this message]
2004-07-06 9:26 ` David Kastrup
2004-07-06 9:46 ` Juanma Barranquero
2004-07-06 10:31 ` David Kastrup
2004-07-06 11:05 ` Juanma Barranquero
2004-07-06 11:42 ` David Kastrup
2004-07-06 12:33 ` Juanma Barranquero
2004-07-06 12:17 ` Stefan
2004-07-06 12:50 ` David Kastrup
2004-07-06 13:08 ` Stefan
2004-07-06 14:13 ` David Kastrup
2004-07-06 14:39 ` David Kastrup
2004-07-06 15:26 ` Stefan
2004-07-06 17:18 ` David Kastrup
2004-07-07 13:28 ` Stefan
2004-07-07 13:45 ` David Kastrup
2004-07-07 14:22 ` Stefan
2004-07-07 14:28 ` David Kastrup
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=20040706104047.587A.JMBARRANQUERO@wke.es \
--to=jmbarranquero@wke.es \
--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).