From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 10571 invoked from network); 2 Oct 2023 03:47:41 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 2 Oct 2023 03:47:41 -0000 Received: from wopr.sciops.net ([216.126.196.60]) by 9front; Sun Oct 1 23:40:39 -0400 2023 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sciops.net; s=20210706; t=1696218012; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=/Q/n2q3AzGwGmsVnuB8KIa03OdDHL7uOiG0BIh3BHu0=; b=T8BW66RW5Eso4q9DvZX/r30/ttQQNM8AujTvgRM8hAAhdHEnoGUUZNV4XPfHiBvYGAx0hp BYpp5TiCb+ya+IfdK/dv693TEWfJZjkdEhUtBRoQQL69h0gUoPcX0PkZohClLD5daQ4VJ+ KdAlQuNLW8FdOwM4Qsm8ApumTc4uqOo= Received: from localhost (wopr.sciops.net [local]) by wopr.sciops.net (OpenSMTPD) with ESMTPA id b96d4501 for <9front@9front.org>; Sun, 1 Oct 2023 20:40:12 -0700 (PDT) Date: Sun, 1 Oct 2023 20:40:12 -0700 From: Kurt H Maier To: 9front@9front.org Message-ID: Mail-Followup-To: 9front@9front.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: stable responsive realtime extension strategy rails Subject: Re: [9front] [PATCH] git: add missing usages for subcommands Reply-To: 9front@9front.org Precedence: bulk On Sun, Oct 01, 2023 at 04:34:00PM -0700, unobe@cpan.org wrote: > > What if, in the long-form area that expanded on the different git > programs, the ones which aren't meant to be used directly are > mentioned as such? For me, some documentation of all programs is more > useful than none, even ones meant for internal-use only? Something > like this at the end: > "Git/get, git/repack, git/save, and git/send are primarily internal > commands, and therefore not documented beyond their usage lines above > and their own code." the traditional approach is for ori, or an intern, to write a paper about this git implementation, so it can live in /sys/doc. I assume, for the sake of argument, that ori has unlimited free time and interns to accomplish this, and so I look forward to reading the paper when it is published, for the sake of argument, later today. khm