[EMAIL PROTECTED] writes:
| On Sat, 11 Nov 2000, R. Lahaye wrote:
| > I believe 1.1.6 will have a big impact on the docs.
| > So many things have changed (dialogs, menus, bug-fixes etc.).
| >
| > The docs in cvs are according to the current official release
| > of 1.1.5, but they can't be modified to 1.1.6 overnight after
| > its official release!!
|
| Greetings,
|
| This snippet appeared in the lyx-docs list a week or so ago, and echoes
| the concerns I expressed in the devel group a few weeks back. Since I have
| actually received at least one doc patch from a developer specific to
| 1.1.6 (name withheld to protect his developer reputation :-), I would like
| to formally request that a new CVS branch be made for lyxdoc - probably
| with "lyxdoc" for the new documentation and "lyxdoc_1.1.5" for the 1.1.5
| stuff, similar to the source code branches, and with the same user access
| as now. Lars, (and/or whoever else controls this stuff), can this be done
| soon? (Is this something that I could in principle do? I'm pretty ignorant
| of the magic of CVS ...) Any arguments to the contrary?
I'd rather just place a tag at the current spot and then you get the
the old documentation by
cvs checkout -r lyxdoc-1_1_5
perhaps also make a branch tag there is some futurue alterations are
needed.
Then you can go ahead and modify the rest of the docfiles and update
them.
And _yes_ this is something you should be able to do.
What you want to do is:
1. create a tag at the durrent point
cvs rtag lyxdoc-1_1_5 lyxdoc
2. create a branch tak on the that tag
cvs rtab -b -r lyxdoc-1_1_5 lyxdoc-1_1_5-BRANCH lyxdoc
3. continue working on the HEAD.
Lgb
