[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Syncing Gnus and Emacs repositories

From: YAMAMOTO Mitsuharu
Subject: Re: Syncing Gnus and Emacs repositories
Date: Sat, 16 Jun 2007 22:55:01 +0900
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (Shij┼Ź) APEL/10.6 Emacs/22.1.50 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)

>>>>> On Sat, 16 Jun 2007 15:13:40 +0200, David Kastrup <address@hidden> said:

> Frankly, I don't see the point in not merging either.  I don't see
> that the trunk accomplishes _any_ function in connection to Emacs
> development that would not equally well be accomplished if unicode-2
> was merged.  We don't need a "stable" trunk: we have EMACS_BASE_22
> for that purpose.

I had an impression (yes, just an impression) that:

  EMACS_BASE_22: to become the next bugfix release 22.2.
    Only bugfix changes should go there.
  trunk: to become EMACS_BASE_22 after the 22.2 release.
    Changes common to 22 and 23 should go there.
  emacs-unicode-2: to become the trunk after the 22.2 release.
    Changes specific to 23 (but not multi-tty-specific) should go there.
    Changes made to the trunk also go there by regular sync. by Miles.

But as Richard said multi-tty changes could also go to the trunk under
a certain condition, this impression will never be true at least in a
strict sense.

                                     YAMAMOTO Mitsuharu

reply via email to

[Prev in Thread] Current Thread [Next in Thread]