Fetching full CVS tree (-current -stable) by /usr/bin/cvs

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Fetching full CVS tree (-current -stable) by /usr/bin/cvs

Denis Lapshin-2
I'm using cvsync currently, but it is not so secure as SSH wrapped
/usr/bin/cvs fetching.

According to OpenBSD FAQ: https://www.openbsd.org/anoncvs.html
I can follow -stable -or current by executing separate commands and it
seems I should have to separate directories for -current and -stable.

May I fetch from public available anonymous CVS servers full cvs repo
with -current and -stable branches to have them locally by single
/usr/bin/cvs command like: cvs -qd [hidden email]:/cvs
checkout

Please advice

Reply | Threaded
Open this post in threaded view
|

Re: Fetching full CVS tree (-current -stable) by /usr/bin/cvs

Janne Johansson-3
Den ons 5 dec. 2018 kl 14:07 skrev Denis <[hidden email]>:
> I'm using cvsync currently, but it is not so secure as SSH wrapped
> /usr/bin/cvs fetching.
>
> According to OpenBSD FAQ: https://www.openbsd.org/anoncvs.html
> I can follow -stable -or current by executing separate commands and it
> seems I should have to separate directories for -current and -stable.

cvsync gets you a clone of the repo, "cvs co" gets you a checkout, which for
cvs (and svn, but not git) is not the same, which is why you would have two
separate dirs, one where you checked out -current and one where you track
the -stable branch.

> May I fetch from public available anonymous CVS servers full cvs repo
> with -current and -stable branches to have them locally by single
> /usr/bin/cvs command like: cvs -qd [hidden email]:/cvs
> checkout

.. which makes this part moot, since the cvs command will not collect
all branches
but only the one you specify or -current if you don't.

--
May the most significant bit of your life be positive.