git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: lyle.ziegelmiller@gmail.com
Cc: 'Johannes Schindelin' <Johannes.Schindelin@gmx.de>,
	"'brian m. carlson'" <sandals@crustytoothpaste.net>,
	git@vger.kernel.org
Subject: Re: ! [remote rejected] master -> master (unpacker error)
Date: Thu, 27 Feb 2020 17:58:52 -0500	[thread overview]
Message-ID: <20200227225852.GA1370873@coredump.intra.peff.net> (raw)
In-Reply-To: <004201d5edb4$3dc34040$b949c0c0$@gmail.com>

On Thu, Feb 27, 2020 at 01:24:04PM -0800, lyle.ziegelmiller@gmail.com wrote:

> " But I vividly remember that there used to be a problem even with
> `git.exe`, probably still is a problem on older Windows versions. That might
> be the problem here?"
> 
> I'm using the latest version of Windows 10 and Cygwin's version of git -
> version 2.21.0. This is being executed in a Cygwin window, not a DOS
> terminal.
> 
> All of this stuff used to work.

If you have a version of Git that works and one that doesn't, it might
be worth using git-bisect to find the commit that introduced the
problem. That does imply being able to build from source; I don't know
how hard that is on cygwin.

-Peff

  reply	other threads:[~2020-02-27 22:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16 16:10 ! [remote rejected] master -> master (unpacker error) lyle.ziegelmiller
2020-02-16 21:16 ` brian m. carlson
2020-02-17 16:25   ` lyle.ziegelmiller
2020-02-17 17:17     ` brian m. carlson
2020-02-17 22:45     ` Randall S. Becker
2020-02-18  5:19   ` Jeff King
2020-02-27 21:04     ` Johannes Schindelin
2020-02-27 21:24       ` lyle.ziegelmiller
2020-02-27 22:58         ` Jeff King [this message]
2020-02-28 22:53         ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200227225852.GA1370873@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=lyle.ziegelmiller@gmail.com \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).