public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man-pages.7: Document CAVEATS section
Date: Wed, 27 Jul 2022 11:23:54 +0200	[thread overview]
Message-ID: <95d31ab9-fdc7-2629-0f9c-b2ed30722e30@gmail.com> (raw)
In-Reply-To: <YuEB5INpOo+/UqmG@asta-kit.de>

Hi Ingo,

On 7/27/22 11:14, Ingo Schwarze wrote:
> Hi Alejandro,
> 
> Alejandro Colomar wrote on Tue, Jul 26, 2022 at 09:02:40PM +0200:
> 
>> Thanks for the investigation.  Committed, with a similar commit message
>> (changing references to man(7) by "manual pages", since I consider
>> mdoc(7) pages as relevant in this regard).
> 
> Your commit cb828372 looks good, thanks!
> 
> The following is certainly not a big deal, just mentioning it because
> chances are this may not have been the last time i contributed
> something to your project.

I hope it's not the last :)

> 
> In commit histories, release notes and the like, i prefer being
> credited as Ingo Schwarze <schwarze@openbsd.org> rathen than
> <schwarze@usta.de>.  The reason is that in a hundred years from
> now, i expect people will still know what openbsd.org is, but it
> seems rather unlikely they would still know what usta.de was.
> 
> You may wonder why i rarely use @openbsd.org in my From: headers.
> The reason is that i want to avoid the wrong impression that all my
> mails were official statements of the OpenBSD project.  While many
> opinions i voice might also be shared by some other OpenBSD developers,
> some clearly are not.  And disclaimers in a signature are annoying.
> There is less risk that people think i'm speaking for the UStA of
> the University of Karlsruhe.  :-)
> 
> Probably i should try to remember saying "if you credit me,
> please use this address: ..." when a commit is obviously imminent.
> I often forget because the vast majority of messages that credit me
> are inside OpenBSD, and there it goes without saying.

Sure, I'll try to remember.

Cheers,

Alex

> 
> Yours,
>    Ingo

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

      reply	other threads:[~2022-07-27  9:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 12:08 [PATCH] man-pages.7: Document CAVEATS section Alejandro Colomar
2022-07-26 13:54 ` Ingo Schwarze
2022-07-26 14:29   ` Alejandro Colomar
2022-07-26 15:37     ` Ingo Schwarze
2022-07-26 19:02       ` Alejandro Colomar
2022-07-27  9:14         ` Ingo Schwarze
2022-07-27  9:23           ` Alejandro Colomar (man-pages) [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

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

  git send-email \
    --in-reply-to=95d31ab9-fdc7-2629-0f9c-b2ed30722e30@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=schwarze@usta.de \
    /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