git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matthias Andree" <matthias.andree@gmx.de>
To: "Eric Blake" <ebb9@byu.net>, git@vger.kernel.org
Subject: Re: Git-SVN on Cygwin: svn+ssh good, https awkward
Date: Thu, 23 Apr 2009 20:16:00 +0200	[thread overview]
Message-ID: <op.usuqcyp81e62zd@balu.cs.uni-paderborn.de> (raw)
In-Reply-To: <loom.20090423T175124-165@post.gmane.org>

Am 23.04.2009, 19:58 Uhr, schrieb Eric Blake <ebb9@byu.net>:

>> 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.

Hi Eric,

thanks for the hints and pointers to Cygwin 1.7 beta, however I'd suggest  
to make such changes upstream (i. e. in git.git) for the benefit of  
everybody else.

It also looks to me as though minor changes in the actual baseline Git  
code may be sufficient to get git-svn working on Cygwin 1.5 (stable)  
already. I'd prefer such a minor intrusion to hacking away on forks. :-)

Otherwise I'd start looking at how git-svn handles https:// and svn+ssh://  
methods differently from each other next week or so.

Looking forward to further insights.

-- 
Matthias Andree

  reply	other threads:[~2009-04-23 18:17 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
2009-04-23 18:16   ` Matthias Andree [this message]
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=op.usuqcyp81e62zd@balu.cs.uni-paderborn.de \
    --to=matthias.andree@gmx.de \
    --cc=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 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).