From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.0 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 844EB1FC34 for ; Fri, 8 Dec 2017 22:47:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753130AbdLHWrc convert rfc822-to-8bit (ORCPT ); Fri, 8 Dec 2017 17:47:32 -0500 Received: from elephants.elehost.com ([216.66.27.132]:60939 "EHLO elephants.elehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752730AbdLHWrb (ORCPT ); Fri, 8 Dec 2017 17:47:31 -0500 X-Virus-Scanned: amavisd-new at elehost.com Received: from gnash (CPE00fc8d49d843-CM00fc8d49d840.cpe.net.cable.rogers.com [99.229.136.74]) (authenticated bits=0) by elephants.elehost.com (8.15.2/8.15.2) with ESMTPSA id vB8MlPeM013200 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 8 Dec 2017 17:47:26 -0500 (EST) (envelope-from rsbecker@nexbridge.com) From: "Randall S. Becker" To: "'Junio C Hamano'" Cc: "'Jeff King'" , "=?utf-8?Q?'=C3=86var_Arnfj=C3=B6r=C3=B0_Bjarmason'?=" , References: <008d01d36e48$747cc130$5d764390$@nexbridge.com> <877eu0uvb2.fsf@evledraar.gmail.com> <20171206084833.GA9501@sigill.intra.peff.net> <002601d36ea8$ea80b160$bf821420$@nexbridge.com> In-Reply-To: Subject: RE: Documentation Breakage at 2.5.6 Date: Fri, 8 Dec 2017 17:47:19 -0500 Message-ID: <003301d37076$846d3e00$8d47ba00$@nexbridge.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8BIT X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQFJqr9tdoz5nNh/MRDCzDickCDUBQFCj0pwAi1FvPkBEIVPoAKceD/HpBSvZgA= Content-Language: en-ca Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org -----Original Message----- On December 8, 2017 5:29 PM Junio C Hamano wrote: >"Randall S. Becker" writes: >> One request to Junio: Would it be possible to tag the commits to align >> with the tags in the main repo? That way, I can build a nice little >> Jenkins job to automatically fetch the correct commit for man pages >> when packaging up a release. >I am not interested in doing anything more than absolute minimum in the history that records generated cruft. We already describe the mainline commit object names in the messages; perhaps that is >sufficient? > commit daa88a54a985ed1ef258800c742223c2a8f0caaa > Author: Junio C Hamano > Date: Wed Dec 6 10:04:03 2017 -0800 > > Autogenerated manpages for v2.15.1-354-g95ec6 >The primary reason why I do not want to tag them is because the tree the documentation sources were taken from is *not* the only thing that affects these autogenerated cruft. The AsciiDoc toolchain that >happen to be installed on the box the day I ran the documentation tools is an obvious difference, and I do not want to make them appear any more definitive and official. "This is *the* manpage for release >v2.15.1" is the message I do not want to give. No worries. I will push on with trying to get asciidoc to build so that I can generate the man pages. That probably won't happen soon, so I'll keep MacGyvering. I do get generating is the better solution, but I would rather focus my own efforts on keeping up with git (that ports fairly easily and is essential to work life) than burning off $DAYJOB hours on asciidoc and/or xmlto. Cheers, Randall