From owner-freebsd-questions@freebsd.org Wed Dec 27 02:37:34 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9011BE96625 for ; Wed, 27 Dec 2017 02:37:34 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4234872962 for ; Wed, 27 Dec 2017 02:37:33 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id vBR2bPNr041332 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 26 Dec 2017 20:37:25 -0600 (CST) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id vBR2bPXI041331; Tue, 26 Dec 2017 20:37:25 -0600 (CST) (envelope-from bob) Date: Tue, 26 Dec 2017 20:37:25 -0600 From: Bob Willcox To: Lowell Gilbert Cc: freebsd-questions@freebsd.org Subject: Re: How do I recover a lost ports directory with svn? Message-ID: <20171227023725.GE15686@rancor.immure.com> Reply-To: Bob Willcox References: <20171226162754.GE99670@rancor.immure.com> <44bmilcm0f.fsf@lowell-desk.lan> <20171226194710.GG99670@rancor.immure.com> <44373wdi5p.fsf@lowell-desk.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44373wdi5p.fsf@lowell-desk.lan> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2017 02:37:34 -0000 On Tue, Dec 26, 2017 at 09:22:10PM -0500, Lowell Gilbert wrote: > Bob Willcox writes: > > > On Tue, Dec 26, 2017 at 02:44:16PM -0500, Lowell Gilbert wrote: > >> Bob Willcox writes: > >> > >> > Unfortunately the documentation for > >> > svn seems skimpy (at best) > >> > >> Not so. Every command has extensive help, and there's a whole book on > >> the subversion website explaining the concepts. > > > > I get the availability of the book (which I don't have), but I'd hardly claim > > that the provided command help is extensive. Hardly more than traditional Unix > > Usage info. > > That's fair. The help messages are enough for me to work out syntax > without going back to first principles, but, yes, that's pretty much > what I expect from a man page. > > > Personally, I would much prefer a real man page. > > Funny you should mention that. Some years back, I bashed out a script > that turned the svn help into a browsable document. I can't find that > tool in a quick search of my backups, and I don't even remember whether > it converted things into HTML or info files. [As an emacs user, info is > roughly equivalent to HTML for such things; I have no idea how info can > be useful if you aren't using emacs to browse the docs.] > > But the point is that I found the cross-link information fairly easy to > parse. And once you can do that, you can turn it into anything useful. > > Be full. Well, I guess I was hoping to figure out why the 'svn up' command wasn't getting me back the missing swig13 directory. I think I understand that now (bapt removed it), but at the time it was frustrating. I've written my share of man pages over the years and do believe that a good manpage provides more information and insight to the usage of a command than the svn help does (I find the pkg man pages quite helpful, for example). Bob -- Bob Willcox | If everything is coming your way, you're in the bob@immure.com | wrong lane. Austin, TX |