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

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

>
>
> > > 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).
> >
> > As long as this means to just run a not so complicated perl script, this
> > Could even be done in a commit hook.
>
> I actually was thinking about something automatic which does not require
> any of the busy msysGit developers to do something manual every once in a
> while.


I thought that a commit hook, was something automatic (iff the busy
developers
do commit something once in a while). I guess I can even set this up very
easily
(given push rights, otherwise it will involve manual labor again).



> > Just another question. How does the (msys)git community feel about
> > adding CMake support ? I can probably do that quite easily.
>
> There was somebody who strongly favored CMake over any other solution but
> was not willing to maintain it in the long run (also, I have to admit that
> I have had quite a few problems with CMake, but maybe I am just pampered
> by projects that Just Compile...)
>

The current way of generating a MSVC project is rather outdated, so the
worst
thing that can happen is that you have a different build system which is not
maintained. At least the CMake people will continue to improve on their
side.

Vincent

[-- Attachment #2: Type: text/html, Size: 2011 bytes --]

  reply	other threads:[~2011-11-02  0:39 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
2011-11-01 22:51           ` [msysGit] " 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 [this message]
2011-11-02  0:48           ` 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=CAAH6HY81WNWu2Dj7RA+Rwm8avNzC7TyS0rMJwZECNZuuSO-WVQ@mail.gmail.com \
    --to=vfr@lyx.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=blees@dcon.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kusmabite@gmail.com \
    --cc=msysgit@googlegroups.com \
    --cc=ramsay@ramsay1.demon.co.uk \
    /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).