[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Proposal for a 22.2/trunk development model
From: |
David Kastrup |
Subject: |
Re: Proposal for a 22.2/trunk development model |
Date: |
Sat, 16 Jun 2007 18:41:33 +0200 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (gnu/linux) |
Dan Nicolaescu <address@hidden> writes:
> David Kastrup <address@hidden> writes:
>
> > Dan Nicolaescu <address@hidden> writes:
> >
> > > Richard Stallman <address@hidden> writes:
> > >
> > > > I have decided that we should not merge unicode-2 until a
> > > > couple of months have gone by and we know what should be
> > > > done about Emacs 22.2. Until then I want to avoid
> > > > far-reaching changes in the trunk. Please stop making a
> > > > fuss about a couple of months.
> > > >
> > > > However, it is ok to add new features which are not so
> > > > far-reaching in their effects on the code. Even the
> > > > multi-tty branch could be merged in (once we decide what
> > > > to do about the environment).
> > >
> > > This development model would undoubtedly achieve the goal of being
> > > able to make a high quality 22.2 release.
> >
> > Undoubtedly? Richard is talking about the trunk, you are
> > talking about 22.2 which is to be done off EMACS_22_BASE. So I
> > don't see the two areas actually related, _unless_ one plans to
> > _scrap_ EMACS_22_BASE and basically copy trunk over it. Which
> > nobody has proposed, and which I'd consider an even worse idea
> > than quite a few others I have blown my top over.
>
> Your attitude is completely puzzling to me. I made a concrete,
> constructive proposal to RMS to try to move things in the direction
> that you seem to want too. Instead of waiting for his reply (as I
> politely asked)
Since Richard _has_ already declared the trunk open for new
development, there is no point in asking him to declare the trunk open
for new development _again_. There is also no point in waiting for
him to do so _unless_ you are of the opinion that he changed his mind
about that.
> and try to have a constructive discussion after that, you chose to
> be destructive and nitpick my proposal.
There is simply no point in proposing things (or rather wordings) that
have already been agreed upon. The differences here are about what it
_means_ to have the trunk open for new development. It _is_ already
declared so by Richard.
> Sorry, but I think that a discussion along the lines you started is
> not going to get anywhere, so I'll stop here.
I also see that the discussion along the lines I started (namely that
among the three unicode-2, trunk, EMACS_22_BASE there clearly is one
too many for sensible development focused on a 22.2 and a 23.1
release) is not going anywhere. But discussing some other problem
which we have tackled already does not seem like a useful alternative.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
- Re: Syncing Gnus and Emacs repositories, (continued)
- Re: Syncing Gnus and Emacs repositories, David Kastrup, 2007/06/19
- Re: Syncing Gnus and Emacs repositories, Kenichi Handa, 2007/06/18
- Re: Syncing Gnus and Emacs repositories, Eli Zaretskii, 2007/06/19
- Re: Syncing Gnus and Emacs repositories, Giorgos Keramidas, 2007/06/23
- Re: Syncing Gnus and Emacs repositories, Richard Stallman, 2007/06/16
- Proposal for a 22.2/trunk development model (was: Syncing Gnus and Emacs repositories), Dan Nicolaescu, 2007/06/16
- Re: Proposal for a 22.2/trunk development model, David Kastrup, 2007/06/16
- Re: Proposal for a 22.2/trunk development model, Dan Nicolaescu, 2007/06/16
- Re: Proposal for a 22.2/trunk development model,
David Kastrup <=
- Re: Proposal for a 22.2/trunk development model, Dan Nicolaescu, 2007/06/16
- Re: Syncing Gnus and Emacs repositories, Richard Stallman, 2007/06/15
- Re: Syncing Gnus and Emacs repositories, Jay Belanger, 2007/06/14
- Re: Syncing Gnus and Emacs repositories, Reiner Steib, 2007/06/17
Re: Syncing Gnus and Emacs repositories, Miles Bader, 2007/06/14