Merging Legacy Branches (was: semi-1_14_7 release)

[David Abrahams <dave@boostpro.com>]

At Sat, 23 Jan 2010 13:33:31 +0900,
KATOH Yasufumi wrote:
> 
> >>> On Fri, 22 Jan 2010 08:26:26 +0900
>     in message   "Re: semi-1_14_7 release"
>                   Katsumi Yamaoka-san wrote:
> 
> > Agreed.  The present situation arrests the growth of APEL, FLIM
> > and SEMI.  We must very much thank Morioka-san for his great
> > works, but it's time to let him step down to make way for highly
> > motivated people.  What you should do will be only to declare
> > that you are the maintainer of those CVS repositories in
> > cvs.m17n.org.  Japanese people support it, don't you?  (Simply
> > respond as `Agreed' or write objection.)
> 
> Agreed.
> 
> Now, There are a lot of branches in semi and flim. I want to merge
> those functions if necessary. I cannot understand which branch has any
> function.
> 
> For instance, I use EMIKO-EasyPG that is one of the branch (?) of
> SEMI, because I want to use EasyPG. But I don't know the relation
> between EMIKO-EasyPG (or those branches) and semi-1_14 trunk.

That tag doesn't seem to be in the repository.  I presume you mean
emiko-epg?

  http://github.com/techarcana/semi/tree/emiko-1_14-epg

I'm sure merging things like this into dev would be easy using Git,
but I want to understand what I'm doing first.  I've started a wiki
page for describing legacy branches of SEMI that people would like
merged.  If you all could please fill out any information you know
there, I'd be very grateful:

  http://wiki.github.com/techarcana/semi/legacy-branches

Naturally, we may want to start similar pages for the APEL, FLIM, and
WL itself.

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