Hi Norman,
> I'm losing my mind!
>
> I have just discovered a posting entitled 'Checking out the B_Release
> Branch' in my archives of the Docs mailing list. It is dated 12th
> October 2011 at 09:14. It appears that I wrote it - a full set of
> instructions on checking out the B_Release branch.
I'm losing my mind!
I have just discovered a posting entitled 'Checking out the B_Release
Branch' in my archives of the Docs mailing list. It is dated 12th
October 2011 at 09:14. It appears that I wrote it - a full set of
instructions on checking out the B_Release branch.
Sigh!
Cheers,
Norm.
Hi Paul,
> OTTOMH: cvs -co manual -r B_Release -- or something like that
Close! no hyphen before "co", but:
norman@hubble:~/SourceCode/cvs/firebird/manual> cvs co manual -r B_Release
Password:
cvs server: cannot find module `-r' - ignored
cvs server: cannot find module `B_Release' - ignored
cvs
Hi Norman,
> >> Now, how do I check out the b_release branch please?
> > On the command line: cvs co -r B_Release
> The above no longer appears to work:
>
> norman@hubble:~> cd SourceCode/cvs/firebird/manual/
> norman@hubble:~/SourceCode/cvs/firebird/manual> cvs co -r B_Release
> cvs [checkout abo
Afternoon all,
after a disk tidy and reinstall, I've been recreating all my docs stuff
on my laptop. My backup system doesn't back it up as it is quite simple
to recreate from cvs. At least, I thought so.
I have the web and manual modules recreated and that's fine, but nothing
I do will find t
Hi Norman,
>> - The third way is not very subtle, and frowned upon by CVS gurus, but very
>> robust (in our case!): You have two working copies like above. You work in
>> the first one (the trunk). When you're going to publish, you bluntly copy
>> the file(s) in question over their counterparts
Hi Paul,
I've just updated a number of command line manuals to incorporate
Firebird 2.5 and I have committed them to the normal manual module. So
far so good!
> - If you're fluent in CVS, you can first commit to HEAD, tag the file(s),
> then switch your local copy of the file(s) to B_Release,
Hi all,
See the previous message in this thread.
There's one little problem left: Currently, everything in B_Release is
identical to HEAD (at least as it was yesterday afternoon). Thus, the B_Release
branch probably contains some unpublishable documents.
I'm checking my own manuals to see if t
Hi all,
If you have write access to the manual module, please read this message
carefully.
Yesterday, I have created a CVS branch called B_Release. This branch is
intended for all the *published* (or at least *buildable and publishable*)
revisions of our documents.
The idea is that, for most
