Hi Norman,
> Is it possible to set up a branch under the trunk and another under
> the same position in the B_Release? Or is that not possible.
Yes, you can set up branches on branches, and branches on branches on
branches, and so on.
But "the same position" is not defined between branches and t
Hi Paul,
Re your questions on the branching set up for V3 docs.
I'm not a CVS expert by any means, so if I'm being stupid in what
follows, just laugh and ignore me! ;-)
Is it possible to set up a branch under the trunk and another under the
same position in the B_Release? Or is that not possi
Hi all,
> > Are the benefits worth the trouble? And what happens with our history
> > if we move to git?
> I don't know this. There are tools to migrate Subversion, for example,
> that I know of. I don';t know of a CVS one nor whether the history comes
> too.
>
> I think a V3 branch in the existi
On 13/08/13 10:24, Paul Vinkenoog wrote:
> Are there any opinions on this? My own knowledge of git is zero.
Mine is slightly better than zero. I quite like git and subversion, but
they are completely different beasts. Git has the advantage that I can
do work and commit stuff even though my inter
13.08.2013 13:24, Paul Vinkenoog wrote:
>
> Are there any opinions on this? My own knowledge of git is zero.
I see zero value in switching, especially with our huge number of
changes being committed daily
Dmitry
--
G
Hi all,
>I would suggest to move all documentation to git on sf.net or github ,
>it is a lot easier to manage branches also faster and use firebird
>type of branches
>
>master-> firebird 3.x devel
>firebird_2.5 -> firebird 2.5 documentation
>firebird_2.1 -> firebird 2.1 documentation
>
>https://gi
I would suggest to move all documentation to git on sf.net or github ,
it is a lot easier to manage branches also faster and use firebird
type of branches
master-> firebird 3.x devel
firebird_2.5 -> firebird 2.5 documentation
firebird_2.1 -> firebird 2.1 documentation
https://github.com/asfernand
Hi Norman,
>I've been reading through the Firebird 3 (Alpha) Release Notes this
>morning and I'm seeing a few changes over and above previous versions.
>
>I am suggesting that we start afresh (!) from this release with our
>documents. I know this might be extra work and we all suffer from a lack
>
Morning all,
I've been reading through the Firebird 3 (Alpha) Release Notes this
morning and I'm seeing a few changes over and above previous versions.
I am suggesting that we start afresh (!) from this release with our
documents. I know this might be extra work and we all suffer from a lack
o
