On Wed, Jun 19, 2019, 7:09 PM Alan Somers <asom...@freebsd.org> wrote:

> On Wed, Jun 19, 2019 at 5:38 PM Warner Losh <i...@bsdimp.com> wrote:
> >
> >
> >
> > On Wed, Jun 19, 2019 at 1:14 PM Alan Somers <asom...@freebsd.org> wrote:
> >>
> >> Does anybody know how to check out a local copy of the CSRG
> >> repository?  I can view it with ViewVC, but I would really like local
> >> access.  It doesn't seem to be available on the usual repo.FreeBSD.org
> >> or svn.FreeBSD.org.
> >>
> >> $ svn checkout https://svn.FreeBSD.org/csrg csrg
> >> svn: E170013: Unable to connect to a repository at URL
> >> 'https://svn.freebsd.org/csrg'
> >> svn: E175009: The XML response contains invalid XML
> >> svn: E130003: Malformed XML: no element found at line 1
> >>
> >> $ svn co svn+ssh://asom...@repo.freebsd.org/csrg csrg
> >> svn: E170013: Unable to connect to a repository at URL
> >> 'svn+ssh://asom...@repo.freebsd.org/csrg'
> >> svn: E210005: No repository found in 'svn+ssh://
> asom...@repo.freebsd.org/csrg'
> >
> >
> > Can't answer this question directly about svn
> >
> > But I have been using
> https://github.com/dspinellis/unix-history-repo.git to look at historical
> sources. https://github.com/csrg has a number of additional repos of
> historical interest, though they are all forks from somewhere else.
> >
> > Warner
>
> Thanks for that Github link; it's pretty useful.  Also, I found this
> site to be helpful: https://www.tuhs.org/cgi-bin/utree.pl .  I just
> wish I had a better understanding of the relationship between CSRG and
> the various releases.  It seems like some stuff got committed to CSRG
> yet didn't make it into an official release for years, if ever.
>

TUHS is awesome. I use it too, bit the historical github tree is more
convenient.

CSRG's 4.x series was pretty linear. What didn't make it?

Warner

>
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to