From: Eric Blake <ebb9@byu.net>
To: git@vger.kernel.org
Subject: Re: Git-SVN on Cygwin: svn+ssh good, https awkward
Date: Thu, 23 Apr 2009 17:58:24 +0000 (UTC) [thread overview]
Message-ID: <loom.20090423T175124-165@post.gmane.org> (raw)
In-Reply-To: op.usulh7a71e62zd@balu.cs.uni-paderborn.de
Matthias Andree <matthias.andree <at> gmx.de> writes:
> 3. UNDERLYING CYGWIN LIMITATIONS
>
> * unlink a file and subsequent creation of a new file in the same location
> is not supported.
>
> * "delete on close" (unlinking an open file) is supported.
These last two points are old information. I would first recommend that you
try running the new cygwin 1.7 (still in beta), where unlink() semantics have
been greatly improved (you can actually unlink() an in-use file and recreate a
new file by the same name while the old handle is still open).
http://cygwin.com/#beta-test
> 4. FIX SUGGESTIONS AND QUESTIONS
>
> Can we defer unlink()ing the tempfile until all handles to it are closed?
>
> Can we let complete and wait for all processes that hold handles to the
> tempfile.tmp file before attempting to create a new copy?
>
> Can we use unique tempfile names (timestamps, counter, random number
> generator) instead of the hardcoded "tempfile.tmp"? This is probably a
> good idea anyways to evade symlink attacks.
Although newer cygwin may fix your particular problem, this is not a bad
suggestion for msysgit, so I suspect someone may be bothered enough by this to
write a patch. I, however, will not be the one doing it.
--
Eric Blake
next prev parent reply other threads:[~2009-04-23 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 16:31 Git-SVN on Cygwin: svn+ssh good, https awkward Matthias Andree
2009-04-23 16:40 ` Matthias Andree
2009-04-23 17:58 ` Eric Blake [this message]
2009-04-23 18:16 ` Matthias Andree
2009-04-23 18:32 ` Matthias Andree
2009-04-23 19:03 ` Eric Wong
2009-04-24 17:31 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2009-04-25 12:04 Gregory Petrosyan
2009-05-12 13:47 ` Constantine Plotnikov
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=loom.20090423T175124-165@post.gmane.org \
--to=ebb9@byu.net \
--cc=git@vger.kernel.org \
/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.