From: "Shawn O. Pearce" <spearce@spearce.org>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Do not rename read-only files during a push
Date: Fri, 3 Oct 2008 07:16:28 -0700 [thread overview]
Message-ID: <20081003141628.GV21310@spearce.org> (raw)
In-Reply-To: <20081003102043.GR10544@machine.or.cz>
Petr Baudis <pasky@suse.cz> wrote:
> On Mon, Sep 22, 2008 at 07:20:29PM +0200, Petr Baudis wrote:
> > Win32 does not allow renaming read-only files (at least on a Samba
> > share), making push into a local directory to fail. Thus, defer
> > the chmod() call in index-pack.c:final() only after
> > move_temp_to_file() was called.
> >
> > Signed-off-by: Petr Baudis <pasky@suse.cz>
>
> Ping?
Hmmph. It got dropped by accident. I don't remember seeing this
patch via email, and its not on GMane. I found it on marc and am
applying it right now. Thanks for the reminder.
--
Shawn.
next prev parent reply other threads:[~2008-10-03 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 17:20 [PATCH] Do not rename read-only files during a push Petr Baudis
2008-10-03 10:20 ` Petr Baudis
2008-10-03 14:16 ` Shawn O. Pearce [this message]
2008-10-03 14:19 ` Miklos Vajna
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=20081003141628.GV21310@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).