From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Andrey Chernyshov <chernyshov.andrey@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git for windows
Date: Thu, 28 Jan 2016 09:56:48 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1601280949070.2964@virtualbox> (raw)
In-Reply-To: <56A9D3AA.7070306@gmail.com>
Hi Andrey,
on this mailing list, it is considered impolite to top-post, and it is
also expected to reply-to-all unless there is a very good reason not to.
Currently, you are trying to abuse me as a free help desk, which I do not
appreciate.
This time I am re-Cc:ing the mailing list and reply inline.
On Thu, 28 Jan 2016, Andrey Chernyshov wrote:
> The reason for you not seeing 2 emails I was replying to is that
> initially it was in HTML format which looks like are not acceptable for
> your mail server. So I hit 'reply' and converted to plan text.
Okay, so you were lazy... ;-)
> As for mcve I really have no idea what I could add. I'm not doing
> anything special, just click Push in the GUI and get the error like
> below.
The idea of the "M" in "MCVE" is to make it easier for others to
reproduce. For example, if you test only with PHPStorm and do not bother
to test the plain command-line, then you are expecting others to install
PHPStorm just to help you. You see, some people might take that as a
perfect excuse not to help you at all! Count me in.
And if you reproduce on the bare command-line, you do not even need to
mention PHPStorm to begin with. But you do have to give a step-by-step
list of what you did and what you expected to happen and what happened
instead.
You see, you really *want* to make it easy for others to help you.
Generally a good resource is http://whathaveyoutried.com/ and I tried to
come up with a separate list of good advice at
https://github.com/git-for-windows/git/wiki/Issue-reporting-guidelines
In your particular case, I would also recommend setting the environment
variables GIT_TRACE=1 and GIT_CURL_VERBOSE=1 before re-trying and then
pasting the entire text from the console into a reply (*after* seeing that
nothing obvious sticks out).
Ciao,
Johannes
next prev parent reply other threads:[~2016-01-28 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56A8AAD6.4070404@gmail.com>
[not found] ` <56A8AB7F.8040101@gmail.com>
2016-01-27 11:51 ` git for windows Andrey Chernyshov
2016-01-27 12:49 ` Andrey Chernyshov
2016-01-27 15:32 ` Johannes Schindelin
[not found] ` <56A9D3AA.7070306@gmail.com>
2016-01-28 8:56 ` Johannes Schindelin [this message]
2016-02-01 17:18 Git for Windows Aaron Gray
2016-02-01 17:33 ` Johannes Schindelin
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=alpine.DEB.2.20.1601280949070.2964@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=chernyshov.andrey@gmail.com \
--cc=git@vger.kernel.org \
/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).