public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, linux-man@vger.kernel.org
Subject: Re: [PATCH 2/2] man-pages.7: Update non-breaking space advice.
Date: Sun, 1 Aug 2021 14:30:00 +0200	[thread overview]
Message-ID: <3ace504d-338f-039f-462d-3faffc9af4d1@gmail.com> (raw)
In-Reply-To: <20210801114156.w3hmedegg5574zho@localhost.localdomain>

Hi, Branden,

On 8/1/21 1:41 PM, G. Branden Robinson wrote:
> At 2021-08-01T12:49:39+0200, Alejandro Colomar (man-pages) wrote:
>> $ apt-file find git-send-email
>> git-doc: /usr/share/doc/git-doc/git-send-email.html
>> git-doc: /usr/share/doc/git-doc/git-send-email.txt
>> git-email: /usr/lib/git-core/git-send-email
>> git-email: /usr/share/man/man1/git-send-email.1.gz
>>
>> You should install git-email if you're on Debian.
> 
> Evidently!  Good grief, why is that split off?  <grumble>
> 
>> apt-cache also helps if you don't know the exact name of the
>> git-send-email file:
> 
> Yup, it was more like I did not even imagine that the package had been
> split up like that.  I thought there must be a licensing problem or
> something.

The same happened to me the first time.

I guess it's the way Debian folks do their packaging, breaking 
semantically :) every package into smaller packages.  As send-email 
isn't needed at all for (basic) git usage, it can go into a separate 
package.

I like it.  It reduces the size of every package, and you have more 
control over what you have installed on your system.

Comparing that to the short time that I used Manjaro (Arch-based), where 
I had to install full-blown GUI programs just to get a C library...

> 
>>> I did a web search and did not find any reports that NeoMutt does
>>> violence to Git-formatted patches.  Perhaps it is GMail's fault?  (I
>>> use its SMPTS server to send mail.)  Does someone on this list have
>>> experience with this MUA and/or provider?  Is there a trick?
>>
>> I also use gmail, so their servers shouldn't cause any errors, I
>> guess.  But I'm no expert on emailing.
> 
> Damn.  I really like GPG-signing my outbound mails, especially including
> patches.  I try to exemplify the audit trails I advocate.
> 
>> [sendemail]
>> 	smtpuser = alx.manpages
>> 	smtpserver = smtp.googlemail.com
>> 	smtpencryption = tls
>> 	smtpserverport = 587
>> 	smtpPass = my_password_goes_here
> 
> Thanks!  Without some NeoMutt help, it looks like this is my route
> forward.

If you get it to work while still signing your emails, I'd be interested 
in knowing how you have set it up.

:)


Cheers,

Alex


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-08-01 12:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31  3:45 [PATCH 2/2] man-pages.7: Update non-breaking space advice G. Branden Robinson
2021-07-31 11:42 ` Alejandro Colomar (man-pages)
2021-08-01 10:12   ` G. Branden Robinson
2021-08-01 10:49     ` Alejandro Colomar (man-pages)
2021-08-01 11:41       ` G. Branden Robinson
2021-08-01 12:30         ` Alejandro Colomar (man-pages) [this message]
2021-08-04  6:20           ` G. Branden Robinson
2021-08-03  7:36         ` NeoMutt + GMail signed patches (was Re: [PATCH 2/2] man-pages.7: Update non-breaking space advice.) Alejandro Colomar (man-pages)
2021-08-03  9:34           ` наб
2021-10-17 19:53     ` [PATCH 2/2] man-pages.7: Update non-breaking space advice Alejandro Colomar (man-pages)
2021-11-12 20:33       ` Ping^2: " Alejandro Colomar (man-pages)

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=3ace504d-338f-039f-462d-3faffc9af4d1@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox