From: "Kerry, Richard" <richard.kerry@atos.net>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Emily Shaffer <emilyshaffer@google.com>,
Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Denton Liu <liu.denton@gmail.com>
Subject: RE: [PATCH v2] MyFirstContribution: add avenues for getting help
Date: Wed, 20 Nov 2019 10:45:44 +0000 [thread overview]
Message-ID: <AM0PR02MB3715245F0CB1C7678DA8794F9C4F0@AM0PR02MB3715.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1911192227280.15956@tvgsbejvaqbjf.bet>
> From: git-owner@vger.kernel.org <git-owner@vger.kernel.org> On Behalf
> Of Johannes Schindelin
> Sent: Tuesday, November 19, 2019 9:30 PM
> To: SZEDER Gábor <szeder.dev@gmail.com>
> ... except people with an @outlook.com address (all of their emails will
> bounce) and people who do not know how to suppress HTML in their emails
> (which I believe constitutes the vast majority)...
[RK>] And even those of us who can find the plain/html format selection control may find that our employer's system turns everything into base64 anyway, thus again making it impossible to post to vger. I fully expect this email to reach all those of you who are To or CC, but not to reach vger.
Regards,
Richard.
next prev parent reply other threads:[~2019-11-20 10:45 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 21:53 [PATCH] MyFirstContribution: add avenues for getting help Emily Shaffer
2019-11-15 22:05 ` Denton Liu
2019-11-15 23:03 ` Emily Shaffer
2019-11-15 23:06 ` [PATCH v2] " Emily Shaffer
2019-11-15 23:38 ` Johannes Schindelin
2019-11-16 0:09 ` Jonathan Nieder
2019-11-16 3:05 ` Junio C Hamano
2019-11-18 21:45 ` Emily Shaffer
2019-11-19 1:45 ` Junio C Hamano
2019-11-19 18:49 ` SZEDER Gábor
2019-11-19 21:29 ` Johannes Schindelin
2019-11-19 21:41 ` SZEDER Gábor
2019-11-20 1:50 ` Eric Wong
2019-11-20 11:41 ` Johannes Schindelin
2019-11-20 23:40 ` SZEDER Gábor
2019-11-20 10:45 ` Kerry, Richard [this message]
2019-11-20 11:37 ` Junio C Hamano
2019-11-19 18:25 ` SZEDER Gábor
2019-12-13 1:31 ` [PATCH v3] " Emily Shaffer
2019-12-13 3:00 ` Derrick Stolee
2019-12-13 4:14 ` Emily Shaffer
2019-12-13 4:16 ` [PATCH v4] " Emily Shaffer
2019-12-13 17:20 ` [PATCH v3] " Junio C Hamano
2019-12-13 17:49 ` Emily Shaffer
2019-12-13 18:40 ` Junio C Hamano
2020-01-24 20:09 ` [PATCH v5] " emilyshaffer
2020-01-24 20:35 ` Junio C Hamano
2020-01-24 20:50 ` Emily Shaffer
2020-01-24 20:54 ` Emily Shaffer
2020-01-24 21:11 ` Junio C Hamano
2020-01-24 21:01 ` [PATCH v6] " Emily Shaffer
2020-01-24 21:18 ` Junio C Hamano
2020-01-24 21:20 ` Emily Shaffer
2020-01-24 21:26 ` [PATCH v7] " Emily Shaffer
2020-01-24 21:56 ` SZEDER Gábor
2020-01-24 23:44 ` Junio C Hamano
2020-02-06 1:07 ` SZEDER Gábor
2020-02-06 16:33 ` Junio C Hamano
2020-02-06 19:49 ` Emily Shaffer
2020-02-06 22:13 ` Emily Shaffer
2020-02-14 2:03 ` [PATCH] MyFirstContribution: rephrase contact info Emily Shaffer
2020-02-14 2:10 ` Jonathan Nieder
2020-02-14 17:36 ` Junio C Hamano
2020-01-24 22:05 ` [PATCH v7] MyFirstContribution: add avenues for getting help Junio C Hamano
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=AM0PR02MB3715245F0CB1C7678DA8794F9C4F0@AM0PR02MB3715.eurprd02.prod.outlook.com \
--to=richard.kerry@atos.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=liu.denton@gmail.com \
--cc=szeder.dev@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;
as well as URLs for NNTP newsgroup(s).