Date: Sat, 2 Jan 2021 15:43:04 +0000 From: Graham Perrin <grahamperrin@gmail.com> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: etcupdate, svnlite, documentation etc. following the transition of source to Git Message-ID: <1d6c0954-ca13-b3a0-3e82-c79df594e357@gmail.com> In-Reply-To: <87pn2nu3n8.wl-herbert@gojira.at> References: <c8ed98ef-8324-5a3a-b4ba-850c669b5080@gmail.com> <87lfdctq83.wl-herbert@gojira.at> <f5ba064c-f606-3514-1dba-3735edd9cf8b@gmail.com> <87pn2nu3n8.wl-herbert@gojira.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/01/2021 08:47, Herbert J. Skuhra wrote: >> <https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html>; >> still describes use of `svnlite` (not `git` or `got`) and, I guess, >> might continue to do so for some time. >> >> In this context, is `cd /usr/src` still true? > If you clone the repository to /usr/src instead of e.g. > /usr/src/freebsd-current. Thanks again. I imagine that use cases will _eventually_ include trios of directories, as siblings, for example: /usr/src/doc /usr/src/freebsd-stable /usr/src/ports True: there's the tradition of /usr/ports however with all three things moved, or moving, to Git it seems (to me) sensible to have the source files for ports at /usr/src/ports For consistency. A cohesive approach.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1d6c0954-ca13-b3a0-3e82-c79df594e357>