From: "Bertrand Jacquin" <beber.mailing@gmail.com>
To: "Alex Riesen" <raa.lkml@gmail.com>
Cc: "Christopher Faylor" <me@cgf.cx>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: windows problems summary
Date: Thu, 2 Mar 2006 16:57:42 +0100 [thread overview]
Message-ID: <4fb292fa0603020757q4cd3e80cjbb63d0dc58d19756@mail.gmail.com> (raw)
In-Reply-To: <81b0412b0603020735j603b3518ob5e27a02c531093a@mail.gmail.com>
On 3/2/06, Alex Riesen <raa.lkml@gmail.com> wrote:
> On 3/2/06, Christopher Faylor <me@cgf.cx> wrote:
> >
> > Are we *really* contemplating porting git to native Windows?
> >
>
> Actually, I wasn't thinking about that when I was writing that mail,
> but ... why not?
> Cygwin makes syscalls many times slower, git is very slow on
> windows, users (well, I) want it faster, so if the needed api subset
> can be narrowed down to a reasonable amount of work - I think
> I'd give the idea a try.
Is the goal to have something like a git-turtoise (as {svn,cvs}-turtoise) ?
I personaly think that is could be benefic.
--
Beber
#e.fr@freenode
next prev parent reply other threads:[~2006-03-02 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 14:49 windows problems summary Alex Riesen
2006-03-02 15:23 ` Christopher Faylor
2006-03-02 15:35 ` Alex Riesen
2006-03-02 15:57 ` Bertrand Jacquin [this message]
2006-03-02 19:54 ` Alex Riesen
2006-03-02 19:59 ` Christopher Faylor
2006-03-02 20:07 ` Andreas Ericsson
2006-03-02 16:01 ` Andreas Ericsson
2006-03-02 16:26 ` Alex Riesen
2006-03-02 16:51 ` Shawn Pearce
2006-03-02 15:38 ` Johannes Schindelin
2006-03-02 16:33 ` Alex Riesen
2006-03-02 17:33 ` Johannes Schindelin
2006-03-31 19:25 ` Eric W. Biederman
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=4fb292fa0603020757q4cd3e80cjbb63d0dc58d19756@mail.gmail.com \
--to=beber.mailing@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@cgf.cx \
--cc=raa.lkml@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox