git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Faye-Lund <kusmabite@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	Vincent van Ravesteijn <vfr@lyx.org>,
	git@vger.kernel.org,  ramsay@ramsay1.demon.co.uk,
	msysgit@googlegroups.com,  Karsten Blees <blees@dcon.de>
Subject: Re: Re: [PATCHv2] Compile fix for MSVC
Date: Tue, 1 Nov 2011 21:43:41 +0100	[thread overview]
Message-ID: <CABPQNSb07fRUCqPCX7JbfGW_55etZZtPyP=yuCKV9wJeNP-iQw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.1111011332400.32316@s15462909.onlinehome-server.info>

On Tue, Nov 1, 2011 at 7:40 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi kusma,
>
> On Tue, 1 Nov 2011, Erik Faye-Lund wrote:
>> I've applied the patches to 'devel', verified that the result builds,
>> and pushed it out.
>
> I've applied your patches and made up commit messages. So far, I only
> tested with MSVCE 9.0 (AKA Express 2008) before running out of time.
> Please have a look at the commits (since I could build a git.exe with the
> correct version, I felt comfortable enough to push out to 'devel').

The commits look good to me. Thanks for following up on it :)

> Maybe if someone donates Jenkins resources, we could make an automatic
> branch in the future that has git.sln in it (similar to the 'html' branch
> in git.git).

CloudBees seems to have some kind of a free Jenkins service. Perhaps
it's sufficient?
http://www.cloudbees.com/dev-pricing.cb

  reply	other threads:[~2011-11-01 20:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 19:12 [PATCHv2] Compile fix for MSVC Vincent van Ravesteijn
2011-10-31 19:12 ` [PATCH 1/3] Compile fix for MSVC: Do not include sys/resources.h Vincent van Ravesteijn
2011-10-31 19:12 ` [PATCH 2/3] Compile fix for MSVC: Include <io.h> Vincent van Ravesteijn
2011-10-31 19:12 ` [PATCH 3/3] MSVC: Remove unneeded header stubs Vincent van Ravesteijn
2011-10-31 20:34 ` [PATCHv2] Compile fix for MSVC Junio C Hamano
2011-11-01  0:09   ` [msysGit] " Johannes Schindelin
2011-11-01  3:30     ` Junio C Hamano
2011-11-01 11:56     ` Erik Faye-Lund
2011-11-01 16:45       ` Junio C Hamano
2011-11-01 20:35         ` Erik Faye-Lund
2011-11-01 20:47           ` Junio C Hamano
2011-11-01 18:40       ` Johannes Schindelin
2011-11-01 20:43         ` Erik Faye-Lund [this message]
2011-11-01 22:51           ` Johannes Schindelin
2011-11-01 22:32         ` Vincent van Ravesteijn
2011-11-01 22:40           ` [msysGit] " Johannes Schindelin
2011-11-01 23:33             ` Vincent van Ravesteijn
2011-11-02  0:48           ` [msysGit] " Pat Thoyts
2011-11-02  7:34             ` Vincent van Ravesteijn
2011-11-04 15:39             ` Sebastian Schuberth
2011-11-01  0:36   ` Erik Faye-Lund
2011-11-01  3:30     ` Junio C Hamano

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='CABPQNSb07fRUCqPCX7JbfGW_55etZZtPyP=yuCKV9wJeNP-iQw@mail.gmail.com' \
    --to=kusmabite@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=blees@dcon.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=msysgit@googlegroups.com \
    --cc=ramsay@ramsay1.demon.co.uk \
    --cc=vfr@lyx.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).