From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>
Cc: "'Jeff King'" <peff@peff.net>,
"'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>,
git@vger.kernel.org
Subject: RE: Documentation Breakage at 2.5.6
Date: Fri, 8 Dec 2017 17:47:19 -0500 [thread overview]
Message-ID: <003301d37076$846d3e00$8d47ba00$@nexbridge.com> (raw)
In-Reply-To: <xmqq4lp07t1k.fsf@gitster.mtv.corp.google.com>
-----Original Message-----
On December 8, 2017 5:29 PM Junio C Hamano wrote:
>"Randall S. Becker" <rsbecker@nexbridge.com> 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 <gitster@pobox.com>
> 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
prev parent reply other threads:[~2017-12-08 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 4:12 Documentation Breakage at 2.5.6 Randall S. Becker
2017-12-06 8:14 ` Ævar Arnfjörð Bjarmason
2017-12-06 8:48 ` Jeff King
2017-12-06 15:43 ` Randall S. Becker
2017-12-08 22:29 ` Junio C Hamano
2017-12-08 22:47 ` Randall S. Becker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003301d37076$846d3e00$8d47ba00$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).