git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Chris B <chris.blaszczynski@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: git push --quiet option does not seem to work
Date: Mon, 16 May 2016 17:04:34 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1605161700360.3303@virtualbox> (raw)
In-Reply-To: <CADKp0px3v3K4vqNeNk7NdWZFdSCyqMa+i_Nv0wW80Tkf0C=RUQ@mail.gmail.com>

Hi Chris,

On Mon, 16 May 2016, Chris B wrote:

> Once I included the whole email in my reply, but otherwise I deleted it
> all.

Both are bad practice. If you are considerate with the reader's time, this
consideration is typically reprocicated. So it is a good idea to save the
reader time by giving them the precise context they need.

> Anyway, it is not a Powershell thing. I tested on another repo on
> GitHub and it worked as expected. So I guess indeed the problem lies
> with Microsoft's implementation.

This is *really* unclear.

What "Microsoft's implementation"??? Do you refer to VSTS, or do you refer
to Git for Windows, or PowerShell?

Please. To make it really simple for everybody involved, try to repeat as
closely as possible the same push from PowerShell, Git CMD and Git Bash.
We want to compare oranges to oranges.

FWIW You can repeat the same push by force-pushing the previous state
between re-runs. E.g.

	git push myremote HEAD^:my-branch
	git push myremote my-branch

Ciao,
Johannes

  reply	other threads:[~2016-05-16 15:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 21:21 git push --quiet option does not seem to work Chris B
2016-05-13 22:33 ` Jeff King
2016-05-15 20:29   ` Chris B
2016-05-15 20:34     ` Chris B
2016-05-15 21:23     ` Jeff King
2016-05-16  0:51       ` Chris B
2016-05-16  0:58         ` Jeff King
2016-05-16 13:13           ` Chris B
2016-05-16 13:28             ` Johannes Schindelin
2016-05-16 13:37               ` Jeff King
2016-05-16 14:32                 ` Chris B
2016-05-16 15:04                   ` Johannes Schindelin [this message]
2016-05-16 15:17                     ` Jeff King
2016-05-17  0:06                       ` Chris B

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.1605161700360.3303@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=chris.blaszczynski@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.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).