-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jean-Pierre Sevigny <[EMAIL PROTECTED]> writes:
> Thanks,
>
> I guess tagging the module file at the same time of tagging the module
> would allow to keep track of the module evolution?
Possibly, but cvs would not be able to use that version of the modules
file unless you replaced the version on the trunk.
-- Mark
> Would be cool to allow definition of modules per branches :)
>
> Thanks again for your answer,
>
> JP
>
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >Jean-Pierre Sevigny <[EMAIL PROTECTED]> writes:
> >
> >
> >
> >>Modules are cool!
> >>
> >>
> >
> >Modules have problems as they may be changed over time making it
> >difficult to recapture the state of a checkout from the past.
> >
> >Modules are not branched, so the same module file need to work for all
> >possible branches of the repository.
> >
> >Someone suggested patches to modules to deal with branching once, but I
> >lost track of that suggestion.
> >
> >
> >
> >>Is it possible to declare a module that does a checkout of a branch,
> >>i.e. something like:
> >>
> >>product_A = product branch A
> >>product_B = product branch B
> >>
> >>
> >
> >No.
> > -- Mark
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.2.3 (FreeBSD)
> >
> >iD8DBQFCXVuq3x41pRYZE/gRAjCnAKCbKqbJ8xvb6tTPO9sGoF31oZACIwCcCpAD
> >5w8tDH+ShgFhCsPkxXMmWD4=
> >=DqQm
> >-----END PGP SIGNATURE-----
> >
> >
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCXWlD3x41pRYZE/gRAlsxAJ9ibTHAKEbWvh2TXxDdJ/o4Ic2MOACg2PbE
ZZV3hjBzhg5GXFug/yxyxzs=
=h+RK
-----END PGP SIGNATURE-----
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/info-cvs
