From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Bram Huenaerts <bramhuenaerts@me.com>, git@vger.kernel.org
Subject: Re: Git union issue
Date: Thu, 30 Jul 2020 19:12:09 -0700 [thread overview]
Message-ID: <xmqqpn8c4eme.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200731010541.GI6540@camp.crustytoothpaste.net> (brian m. carlson's message of "Fri, 31 Jul 2020 01:05:41 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> folks will be more likely to read your message. (I was personally
> surprised to see the list accepted PDFs; I did not think it would.)
I am surprised too, and immediately after I saw *.pdf attachment, I
discarded the message to the trash, thinking it is a phishing attempt
or something similar.
prev parent reply other threads:[~2020-07-31 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 18:29 Git union issue Bram Huenaerts
2020-07-31 1:05 ` brian m. carlson
2020-07-31 2:12 ` Junio C Hamano [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=xmqqpn8c4eme.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=bramhuenaerts@me.com \
--cc=git@vger.kernel.org \
--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).