From: Philip Oakley <philipoakley@iee.email>
To: Ernst Reissner <rei3ner@arcor.de>, git@vger.kernel.org
Subject: Re: bugreport on this email address
Date: Tue, 19 May 2020 12:34:28 +0100 [thread overview]
Message-ID: <770f745c-07a2-778c-99a9-5fba5fbb0aea@iee.email> (raw)
In-Reply-To: <f84f24fe-50e0-5e6e-4951-be34b230fb44@arcor.de>
Hi Ernst,
On 19/05/2020 11:42, Ernst Reissner wrote:
> Hello all,
>
> i wanted to file a bugreport and found that this email address shall be
> used in
>
> https://git-scm.com/community
>
> Note that the link is broken.
Which part is broken? do note that this list only accepts plain text
emails - no HTML parts!
>
>
> I hope the address itself is valid.
Correct. This is the correct address for the Git developer community and
the right place to report a bug with (hopefully) a clear description of
the bug, and a simple method for reproducing the bug (preferably without
having to clone some mega repo;-)
>
>
> Greetings,
>
> Ernst
--
Philip
prev parent reply other threads:[~2020-05-19 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 10:42 bugreport on this email address Ernst Reissner
2020-05-19 11:34 ` Philip Oakley [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=770f745c-07a2-778c-99a9-5fba5fbb0aea@iee.email \
--to=philipoakley@iee.email \
--cc=git@vger.kernel.org \
--cc=rei3ner@arcor.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;
as well as URLs for NNTP newsgroup(s).