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

Re: semi-1_14_7 release



At Thu, 21 Jan 2010 08:00:30 +0900,
Katsumi Yamaoka wrote:
> 
> >>>>> In [Wanderlust English : No.03366] David Abrahams wrote:
> > Neither the HEAD nor the 1.14.6 version of semi was not compatible
> > with WL's HEAD, so I checked in and tagged semi-1_14_7.
> 
> You've made a change in the trunk of SEMI CVS repository:
> 
> -------------------- Start of forwarded message --------------------
> From: dave <cvs@cvs.m17n.org>
> Date: Wed, 20 Jan 2010 20:54:59 +0900
> Subject: /cvs/root/semi: Compatibility with latest WL; stop using obsolete...
> Message-ID: <1263988499.32520@cvs.m17n.org>
> List-Help: <mailto:m17n-cvs-info-ctl@m.aist.go.jp?body=help>
> List-Unsubscribe: <mailto:m17n-cvs-info-ctl@m.aist.go.jp?body=unsubscribe>
> 
> Log Message:
> Compatibility with latest WL; stop using obsolete variable names
> 
> Update of /cvs/root/semi
> 
> Main Trunk
> ^^^^^^^^^^
>  mime-view.el: 1.151 -> 1.152
> 
> cvs rdiff -r1.151 -r1.152 semi/mime-view.el
> 
> http://cvs.m17n.org/viewcvs/root/semi/mime-view.el?r1=1.151&r2=1.152
> 
> /cvs/root/semi/mime-view.el 1.152 e76a6ca0290a855b62de120a9266dd3b
> -------------------- End of forwarded message --------------------
> 
> But the bleeding edge now is in the semi-1_14 branch; the recent
> changes have been being made there, and SEMI 1.14 series have been
> being released from there.  The FLIM and SEMI developments are
> being done in the branches although many other developments (e.g.,
> Emacs, Gnus, etc.) are being done in the trunk.  That's the policy
> that Morioka-san, the maintainer, had decided first.  The trunk is
> the place where the final fruit of the development will be put.

I like the policy; thanks for letting me know, and sorry for messing
up the system.  What should I do to correct my error, if anything?

Also, can you tell me which the current branches of FLIM, WL, and APEL
are?

Thanks!

-- 
Dave Abrahams           Meet me at BoostCon: http://www.boostcon.com
BoostPro Computing
http://www.boostpro.com