From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: lyle.ziegelmiller@gmail.com
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: ! [remote rejected] master -> master (unpacker error)
Date: Mon, 17 Feb 2020 17:17:17 +0000 [thread overview]
Message-ID: <20200217171717.GG6134@camp.crustytoothpaste.net> (raw)
In-Reply-To: <001801d5e5ae$e4375780$aca60680$@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
On 2020-02-17 at 16:25:38, lyle.ziegelmiller@gmail.com wrote:
> I wrote a bunch of emails about this in December 2019. Did they all get lost?
No, I don't believe so. However, sometimes people get busy and things
fall through the cracks, so pinging like you did is a good idea.
> I'm consistently able to clone the repository, but I can never push to it. I used to be able to. I've explored all possibilities that I know of.
>
> I'm using Windows 10, and the Cygwin version of Git.
>
> $ git --version
> git version 2.21.0
It looks like you're pushing to a UNC path, and I don't know how that
works with Cygwin. It may be that it used to work, but something
changed in Cygwin or Git.
I've CC'd the Git for Windows maintainer (Dscho) in case he has some
ideas. While he doesn't package the Cygwin Git, he might know what's
going on. I'm not very familiar with Cygwin at all, not being a Windows
user. You could also try reporting this to the Cygwin bug tracker and
see if they can figure things out.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2020-02-17 17:17 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 [this message]
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
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=20200217171717.GG6134@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=lyle.ziegelmiller@gmail.com \
/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).