From: Johannes Sixt <j6t@kdbg.org>
To: Jeff King <peff@peff.net>
Cc: X H <music_is_live_lg@hotmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git force push fails after a rejected push (unpack failed)?
Date: Wed, 08 Jul 2015 22:56:23 +0200 [thread overview]
Message-ID: <559D8E77.60401@kdbg.org> (raw)
In-Reply-To: <20150708180539.GA12353@peff.net>
Am 08.07.2015 um 20:05 schrieb Jeff King:
> We also don't write objects directly, of course; we write to a temporary
> file and try to link them into place. It really sounds more like the
> "objects/d9" directory is where the permission problems are. But, hmm...
Not on Windows: A read-only file cannot be overwritten or removed,
regardless of the permissions of the directory. We do treat this case
mingw_rename, but I have a slight suspicion that this does not work
sufficiently reliably on networked file systems.
-- Hannes
prev parent reply other threads:[~2015-07-08 20:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 13:45 Git force push fails after a rejected push (unpack failed)? X H
2015-07-07 14:13 ` Jeff King
[not found] ` <DUB120-W36B78FEE6DC80BDCB05D7FF6920@phx.gbl>
2015-07-07 19:49 ` Jeff King
2015-07-07 23:05 ` Eric Sunshine
2015-07-08 17:41 ` Johannes Sixt
2015-07-08 18:05 ` Jeff King
2015-07-08 18:33 ` [PATCH] check_and_freshen_file: fix reversed success-check Jeff King
2015-07-08 19:24 ` Junio C Hamano
2015-07-08 20:33 ` [PATCH v2] " Jeff King
2015-07-08 21:03 ` [PATCH] " Johannes Sixt
2015-07-09 20:51 ` Johannes Sixt
2015-07-09 22:48 ` Jeff King
2015-07-11 22:21 ` X H
2015-07-13 3:52 ` Jeff King
2015-07-13 19:58 ` X H
2015-07-08 20:28 ` Git force push fails after a rejected push (unpack failed)? X H
2015-07-08 20:56 ` Johannes Sixt [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=559D8E77.60401@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=music_is_live_lg@hotmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.