From: Junio C Hamano <gitster@pobox.com>
To: "Randall S. Becker" <rsbecker@nexbridge.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, 08 Dec 2017 14:29:11 -0800 [thread overview]
Message-ID: <xmqq4lp07t1k.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <002601d36ea8$ea80b160$bf821420$@nexbridge.com> (Randall S. Becker's message of "Wed, 6 Dec 2017 10:43:03 -0500")
"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.
Sorry, I missed this due to an overlong line in the message.
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
commit 466a3070abecf4081a12d8e07c770689506440b9
Author: Junio C Hamano <gitster@pobox.com>
Date: Wed Nov 29 10:12:49 2017 +0900
Autogenerated manpages for v2.15.1-271-g1a4e4
commit be681f4100647ab93fd19cb5066fcaa2cb79204b
Author: Junio C Hamano <gitster@pobox.com>
Date: Mon Nov 27 12:33:30 2017 +0900
Autogenerated manpages for v2.15.0-374-g5f995
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.
next prev parent reply other threads:[~2017-12-08 22:29 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 [this message]
2017-12-08 22:47 ` Randall S. Becker
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=xmqq4lp07t1k.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=rsbecker@nexbridge.com \
/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).