From: Alex Riesen <raa.lkml@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Sam Vilain" <sam@vilain.net>,
"Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>,
"René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Subject: Re: [PATCH] Use find instead of perl in t5000 to get file modification time
Date: Sun, 2 Nov 2008 15:37:52 +0100 [thread overview]
Message-ID: <20081102143751.GA18140@blimp.localdomain> (raw)
In-Reply-To: <alpine.DEB.1.00.0811012134290.22125@pacific.mpi-cbg.de.mpi-cbg.de>
Johannes Schindelin, Sat, Nov 01, 2008 21:37:14 +0100:
> On Sat, 1 Nov 2008, Alex Riesen wrote:
> > Johannes Schindelin, Sat, Nov 01, 2008 01:23:32 +0100:
> > >
> > > Well, if you install Git for Windows (as opposed to cygwin), it is
> > > minimum hassle, and Perl is delivered right with it.
> >
> > I'd like to try it again, but weren't ther some fatal problems with
> > cygwin1.dll being in PATH? I always work either in Cygwin's bash or just
> > have to have it in PATH, because of the build environment even being
> > strictly Windows based (case-insensitive and alike) just have to use
> > sane tooling in its scripts.
>
> I was talking about Git for Windows, i.e. the result of msysGit (as
> opposed to Git in Cygwin).
>
> So no, there have not been any conflicts with cygwin1.dll in the PATH, as
> far as I can recall. There have been problems with shell utilities being
> found in the Cygwin PATH before being found in the MSys PATH, but I
> thought we just prepended the MSys PATH to avoid that. Haven't checked,
> though.
Ok, I'll give it a try.
> > > P.S.: some guys at the GSoC mentor summit convinced me in at least
> > > trying to fix _their_ problems on msysGit, so chances are good I'll
> > > fix issues you would encounter in the same run.
> >
> > Do you still plan to distribute MinGW with it? It's very nice to be able
> > to track Junio's repo, have own branches and rebuild Git from time to
> > time. For me, at least.
>
> You mean to distribute a minimal MSys environment where you have bash?
> Yes, we have to do that, as there are still too many important parts of
> Git written in Shell.
No, the mingw compiler and libraries. I vaguely remember some talking
about including the build environment into Git distribution.
next prev parent reply other threads:[~2008-11-02 14:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 10:38 [PATCH] Use find instead of perl in t5000 to get file modification time Alex Riesen
2008-10-29 21:54 ` Jeff King
2008-10-30 7:26 ` Alex Riesen
2008-10-30 5:29 ` Sam Vilain
2008-10-31 7:00 ` Alex Riesen
2008-10-31 12:59 ` Peter Harris
2008-10-31 13:45 ` Alex Riesen
2008-10-31 22:14 ` Johannes Schindelin
2008-10-31 23:37 ` Alex Riesen
2008-11-01 0:23 ` Johannes Schindelin
2008-11-01 14:24 ` Alex Riesen
2008-11-01 20:37 ` Johannes Schindelin
2008-11-02 14:37 ` Alex Riesen [this message]
2008-11-02 16:05 ` Johannes Schindelin
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=20081102143751.GA18140@blimp.localdomain \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=rene.scharfe@lsrfire.ath.cx \
--cc=sam@vilain.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 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).