git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Dave Huseby <dwh@linuxprogrammer.org>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
	"Lars Schneider" <larsxschneider@gmail.com>,
	"Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Subject: Re: [PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints
Date: Thu, 13 May 2021 09:50:21 +0200	[thread overview]
Message-ID: <87mtszrrum.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20210512235136.GB10785@localhost>


On Wed, May 12 2021, Dave Huseby wrote:

> On 12.05.2021 10:45, Ævar Arnfjörð Bjarmason wrote:
>>There hasn't been a release of Pine since late 2005, in Alpine the
>>no-strip-whitespace-before-send switch is already the default.
>>
>>This documentation was initially added in 9740d289ee7 (Update
>>SubmittingPatches to add MUA specific notes., 2005-08-26), at this
>>point it's safe to say that it's not useful to anyone anymore, let's
>>remove it.
>
> What is wrong with keeping it in there? My latest version of the
> etiquette patch moves my Mutt MUA config notes to this section on MUAs.
> It could eventually become a somewhat exhaustive reference of MUA
> tweaks. Old tools may not be popular but they sometime have niche uses
> and/or userbases. My recent switch to Mutt has been mixed at best and I
> went back to take a look at mh/nmh to see if I liked it better and I may
> give it a go for a while to kick the tires, likely making me the only
> developer that uses nmh.
>
> Keeping these notes on old tools--at the bottom of documentation no
> less--seems to have little to no "cruft cost" with the potential of
> helping somebody someday, even if nostalgia is the only reason.

I think there's an inherent value in keeping guides like these short and
to the point, and only including those things relevant to most readers.

So I do think that if we're including such a niche guide we're better
off splitting it into another file and linking to it, same with the
whole guide in SubmittingPatches now teaching people to manually craft a
patch without using git-format-patch, another obscure edge case we give
too much space / causes distraction.

In this case though I think saying anything about pine crosses the line
from niche to obscure archaeology. We're inlining a patch for abandoned
software that has a replacement. If we're going to say anything about
Pine in such a list I think it should be:

    Pine: abandoned and has known flowed text bugs, use its successor
    alpine or another MUA instead.

  parent reply	other threads:[~2021-05-13  7:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12  8:44 [PATCH 0/3] SubmittingPatches: a few unrelated minor fixes Ævar Arnfjörð Bjarmason
2021-05-12  8:45 ` [PATCH 1/3] SubmittingPatches: move discussion of Signed-off-by above "send" Ævar Arnfjörð Bjarmason
2021-05-12  9:29   ` Felipe Contreras
2021-06-07 11:02     ` Ævar Arnfjörð Bjarmason
2021-06-07 16:16       ` Felipe Contreras
2021-05-12  8:45 ` [PATCH 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions Ævar Arnfjörð Bjarmason
2021-05-12 12:24   ` Đoàn Trần Công Danh
2021-05-12 22:40   ` Junio C Hamano
2021-05-12  8:45 ` [PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints Ævar Arnfjörð Bjarmason
2021-05-12 23:51   ` Dave Huseby
2021-05-13  6:38     ` Felipe Contreras
2021-05-13 14:45       ` Dave Huseby
2021-05-13 20:08         ` Felipe Contreras
2021-05-17 19:05           ` Dave Huseby
2021-05-13  7:50     ` Ævar Arnfjörð Bjarmason [this message]
2021-05-13 14:42       ` Dave Huseby
2021-06-07 11:03 ` [PATCH v2 0/3] SubmittingPatches: a few unrelated minor fixes Ævar Arnfjörð Bjarmason
2021-06-07 11:03   ` [PATCH v2 1/3] SubmittingPatches: move discussion of Signed-off-by above "send" Ævar Arnfjörð Bjarmason
2021-06-07 15:58     ` Đoàn Trần Công Danh
2021-06-07 11:03   ` [PATCH v2 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions Ævar Arnfjörð Bjarmason
2021-06-07 17:25     ` SZEDER Gábor
2021-06-07 11:03   ` [PATCH v2 3/3] SubmittingPatches: remove pine-specific hints from MUA hints Ævar Arnfjörð Bjarmason
2021-06-07 21:49     ` Johannes Schindelin
2021-06-08  3:50   ` [PATCH v2 0/3] SubmittingPatches: a few unrelated minor fixes Junio C Hamano
2021-07-22 12:11   ` [PATCH v3 0/2] SubmittingPatches: talk about GitHub CI, not Travis + move-only Ævar Arnfjörð Bjarmason
2021-07-22 12:11     ` [PATCH v3 1/2] SubmittingPatches: move discussion of Signed-off-by above "send" Ævar Arnfjörð Bjarmason
2021-07-23  6:36       ` Bagas Sanjaya
2021-07-22 12:11     ` [PATCH v3 2/2] SubmittingPatches: replace discussion of Travis with GitHub Actions Ævar Arnfjörð Bjarmason

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=87mtszrrum.fsf@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=congdanhqx@gmail.com \
    --cc=dwh@linuxprogrammer.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=larsxschneider@gmail.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).