git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: M Hickford <mirth.hickford@gmail.com>,
	 "brian m. carlson" <sandals@crustytoothpaste.net>,
	 git@vger.kernel.org
Subject: Re: [PATCH 4/5] doc: use .adoc extension for AsciiDoc files
Date: Fri, 07 Feb 2025 10:05:09 -0800	[thread overview]
Message-ID: <xmqqtt95fx62.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CAa+6xx885TdKFrpruxHbN80S3RE=STaswnaUz_3QZQ=Q@mail.gmail.com> (D. Ben Knoble's message of "Fri, 7 Feb 2025 12:51:48 -0500")

"D. Ben Knoble" <ben.knoble@gmail.com> writes:

>> Do we pass SubmittingPatches (and CodingGuidelines for that matter)
>> through AsciiDoc?  They do not even have .txt suffix, so I suspect
>> it is not.
>
> I don't know how (I didn't dig), but we do build and package
> HTML-ified SubmittingPatches as both $(git
> --html-path)/SubmittingPatches.{html,txt}. I don't see a build output

I was wondering why we remove SubmittingPatches.txt with "make
clean" there the other day.  There is a Documentation/Makefile
target to create %.txt from % applied for SubmittingPatches.

> for CodingGuidelines, though. (We also package
> ReviewingGuidelines.{html,txt}, but it has a .txt extension.)

Thanks for noticing an annoying inconsistency that must be rectified
independent of brian's topic to help it easier for Editors to
identify the files that are written in AsciiDoc.  If we are shipping
documents that are exclusively meant for Git developers, we should
be shipping all of them together.

Thanks.



  reply	other threads:[~2025-02-07 18:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20  1:55 [PATCH 0/5] Convert AsciiDoc files to .adoc extension brian m. carlson
2025-01-20  1:55 ` [PATCH 1/5] doc: update gitignore for " brian m. carlson
2025-01-20  1:56 ` [PATCH 2/5] editorconfig: add " brian m. carlson
2025-01-20  1:56 ` [PATCH 3/5] gitattributes: mark AsciiDoc files as LF-only brian m. carlson
2025-01-20  1:56 ` [PATCH 4/5] doc: use .adoc extension for AsciiDoc files brian m. carlson
2025-01-20 20:37   ` Jean-Noël Avila
2025-01-20 22:08     ` brian m. carlson
2025-01-20 23:43       ` Junio C Hamano
2025-01-21 21:59         ` Jean-Noël Avila
2025-02-06 20:33   ` M Hickford
2025-02-06 21:14     ` Junio C Hamano
2025-02-06 23:47       ` Junio C Hamano
2025-02-07 17:51       ` D. Ben Knoble
2025-02-07 18:05         ` Junio C Hamano [this message]
2025-02-07 18:29           ` Junio C Hamano
2025-02-07 22:54           ` brian m. carlson
2025-01-20  1:56 ` [PATCH 5/5] Remove obsolete ".txt" extensions " brian m. carlson
2025-01-20 17:55 ` [PATCH 0/5] Convert AsciiDoc files to .adoc extension M Hickford
2025-01-20 20:19 ` D. Ben Knoble

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqtt95fx62.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mirth.hickford@gmail.com \
    --cc=sandals@crustytoothpaste.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. 
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 NNTP newsgroup(s).