Re: Checking out the CSRG repository?

On Thu, Jun 20, 2019 at 7:40 AM Rodney W. Grimes
<freebsd-rwg_at_gndrsh.dnsmgr.net> wrote:
>
> > On 19-06-20 05 h 59, Warner Losh wrote:
> > > On Wed, Jun 19, 2019 at 7:55 PM Alan Somers <asomers_at_freebsd.org> wrote:
> > >
> > >> On Wed, Jun 19, 2019 at 8:41 PM Warner Losh <imp_at_bsdimp.com> wrote:
> > >>>
> > >>>
> > >>>
> > >>> On Wed, Jun 19, 2019, 7:09 PM Alan Somers <asomers_at_freebsd.org> wrote:
> > >>>>
> > >>>> On Wed, Jun 19, 2019 at 5:38 PM Warner Losh <imp_at_bsdimp.com> wrote:
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> On Wed, Jun 19, 2019 at 1:14 PM Alan Somers <asomers_at_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://asomers_at_repo.freebsd.org/csrg csrg
> > >>>>>> svn: E170013: Unable to connect to a repository at URL
> > >>>>>> 'svn+ssh://asomers_at_repo.freebsd.org/csrg'
> > >>>>>> svn: E210005: No repository found in 'svn+ssh://
> > >> asomers_at_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
> > >>
> > >> I'm looking at bmap.  When I wrote that email, the earliest released
> > >> reference I could find was in 4.3-Reno.  However, I just spotted it in
> > >> 4.2, which is a much more reasonable time frame (it moved to a
> > >> different file which is why I missed it before).  However, the files
> > >> in question don't even exist in the git branches from dspinellis's
> > >> repository.  I had to find them on tuhs.org.  Am I doing something
> > >> wrong, or are dspinellis's release branches not fully populated?
> > >> Compare
> > >> https://github.com/dspinellis/unix-history-repo/tree/BSD-4_3_Reno-Snapshot-Development/usr/src/sys/sys
> > >> to https://www.tuhs.org/cgi-bin/utree.pl?file=4.3BSD-Reno/src/sys/sys
> > >
> > >
> > > I'm guessing the SCCS -> SVN -> Git process broke files that were renamed
> > > or copied... I've not dug deeper though... This tells me that we need to
> > > send dspinellis some corrections :)
> > >
> > > Warner
> > > _______________________________________________
> > > freebsd-current_at_freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> > >
> >
> > Replying to an arbitrary message..
> >
> > Using svnweb it so EASY to see that the correct invocation is
> >
> > svn co https://svn.freebsd.org/base/vendor/CSRG
> >
> > as I just done..
>
> Well once you know that it is obvious, I think is what
> is happening is that people go to https://svn.freebsd.org/
> and there is csrg listed there and the paths you get once
> you follow that is wrong from then on.
>
> Maybe obliterarate that top level miss leading link
> would be the right thing to do?  Or put a roadmap
> file at that level in place and then delete that csrg link.
>
> Thank you for pointing us all to where the "real data"
> is at.

No.  base/vendor/CSRG is different.  It just has a dump of a few
things that were imported into base/head.  It doesn't have the full
history of CSRG's work.  You can tell just by looking at the number of
commits.  base/vendor/CSRG only has 73 commits, but the full CSRG repo
has about 1000x as many.

-Alan