List Info

Thread: Re: Branch creation takes a long time




Re: Branch creation takes a long time
country flaguser name
United States
2007-04-06 11:20:07
On Fri, 6 Apr 2007 22:18:27 +1000, Arthur Barrett wrote:

> Colin,
> 
> This can occur under very specific circumstances. 
Basically it gets harder and harder for CVSNT to find the
next free number for a branch.  We've had a patch submitted
that'll be a part of the next next 2.5.04 build in a few
weeks time.  Be sure to keep an eye on this list for the
annoucement.  Also it's an option that needs to be enabled
in the control panel (or on linux in the /etc/cvsnt/PServer
config file).
> 
> More info is available in the bug database under bug
4855.
> http://customer.march-hare.com/webtools/bugzilla/tt.htm
> 
> However that said, this problem only occurs when there
are a LOT of branches, which possibly means that you are not
using CVSNT in an "optimal" way.  Please describe
what business purpose creating so many branches is serving
and we'll also try to point you in a more efficient
direction.
> 
> Regards,
> 
> 
> Arthur Barrett
> 

Hi Arthur,

Don't want to steal the OP thread, but what would you
consider to be a LOT
fo branches?
I work for a manufactoring company and due to the software
design we do an
official release every two weeks to the factory floor. I'm
creating a
branch for each of these and then creating a tag if we need
to release a
bug fix on the build branch. This creates a fair number of
branches and
tags. Too many?
Thanks,
Rick 
_______________________________________________
cvsnt mailing list
cvsntcvsnt.org
h
ttp://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

Re: Branch creation takes a long time
country flaguser name
United States
2007-04-06 12:15:31
Rick Martin wrote:

> Don't want to steal the OP thread, but what would you
consider to be a LOT
> fo branches?
> I work for a manufactoring company and due to the
software design we do an
> official release every two weeks to the factory floor.
I'm creating a
> branch for each of these and then creating a tag if we
need to release a
> bug fix on the build branch. This creates a fair number
of branches and
> tags. Too many?

I'm not sure I understand your procedure correctly, but
couldn't you tag
these official releases, and only branch this tag later if
you actually
need to do some bug fixing? Assuming that fixing bugs in an
official
release is the exception rather than the rule, this would
cut down quite a
bit on the number of branches.

Gerhard
_______________________________________________
cvsnt mailing list
cvsntcvsnt.org
h
ttp://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )