Re: 21.0 vs 21.2

Monday, 4 January 1999

        Tor Arntsen <tor(a)spacetec.no&gt; writes in xemacs-beta(a)xemacs.org:
 ...
...
 With two trees you can still see that they are 'one' source
tree because
 you can do
  cd xemacs-21.2; cvs tag start_myfix INSTALL; <edit INSTALL>
  cvs commit -m "Corrected configure instructions" INSTALL
  cd ../xemacs-22.0; cvs -q update -jstart_myfix -jrelease-21-2 INSTALL
  cvs commit -m "merged fixes from 21.2 branch to 22.0 branch"
 instead of re-implementing the changes in the second branch. 
Cute.  I've never been brave[1] enough to try out stuff like that.  Will
it still work after a lot of changes have been committed?  ie. after
divergence has set in?

Hmmm.  The man page says a date may be used instead of tag.  That
sounds cleaner if it works.

...
 For people with only read access (e.g. like me) the fact that the
two
 versions exist in the same source tree at the repository is of no big
 importance (except for the fact that it's good to know :-) 
...
 (jumping in with too many cvs comments maybe.. it's a habit I
guess, I'm 
 responsible for the cvs stuff where I work) 
Please keep it up.  It's a pity you weren't around in December of
1996 when things were first being set up.

Footnotes: 
[1]  And I'm less brave now after 4 successive 1.10 releases that
don't pass regression tests ... :-(

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998