The problem with tags/branches is on the input side (parsing RCS files), at
least we haven't had good results with cvsps-based tooling or
rcsparse-based. I don't think it will make much difference whether
conversion is by way of svn or not (except there will be extra
conversion-related artefacts going by way of svn).
It could likely be fixed on a one off conversion by repo surgery, but as
the master repo is unlikely to be switched (various reasons already
mentioned in this thread), conversion would need to be on an ongoing basis
without constant tweaks..
--
Sent from a phone, apologies for poor formatting.
On 23 July 2019 19:42:24 Adam Thompson <[email protected]> wrote:
On 2019-07-23 12:43, Stuart Henderson wrote:
On 2019-07-22, Stefan Sperling <[email protected]> wrote:
If your university class prefers using git, I'd recommend the
repository at
https://github.com/openbsd/src.
However, it doesn't include branches/tags, because we haven't found
anything that
is able to successfully convert the OpenBSD CVS repository to git
unless it ignores
these.
I haven't tried this with the OpenBSD code base, but in a previous life
I did a CVS to Git conversion starting with a repo that resembled
OpenBSD's in many ways.
The "solution" was to get to git by way of SVN. SVN was able to
preserve branches/tags/etc. from CVS into SVN, and was then able to in
turn be converted to git through SVN's git-compatibility layer (IIRC).
Whether this helps anyone out there... *shrug*
-Adam
