git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: js/visual-studio, was Re: What's cooking in git.git (Aug 2019, #01; Thu, 1)
Date: Fri, 2 Aug 2019 14:06:35 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1908021405450.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqv9vgmz2f.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Thu, 1 Aug 2019, Junio C Hamano wrote:

> * js/visual-studio (2019-07-29) 23 commits
>  - git: avoid calling aliased builtins via their dashed form
>  - bin-wrappers: append `.exe` to target paths if necessary
>  - .gitignore: ignore Visual Studio's temporary/generated files
>  - .gitignore: touch up the entries regarding Visual Studio
>  - vcxproj: also link-or-copy builtins
>  - msvc: add a Makefile target to pre-generate the Visual Studio solution
>  - contrib/buildsystems: add a backend for modern Visual Studio versions
>  - contrib/buildsystems: handle options starting with a slash
>  - contrib/buildsystems: also handle -lexpat
>  - contrib/buildsystems: handle libiconv, too
>  - contrib/buildsystems: handle the curl library option
>  - contrib/buildsystems: error out on unknown option
>  - contrib/buildsystems: optionally capture the dry-run in a file
>  - contrib/buildsystems: redirect errors of the dry run into a log file
>  - contrib/buildsystems: ignore gettext stuff
>  - contrib/buildsystems: handle quoted spaces in filenames
>  - contrib/buildsystems: fix misleading error message
>  - contrib/buildsystems: ignore irrelevant files in Generators/
>  - contrib/buildsystems: ignore invalidcontinue.obj
>  - Vcproj.pm: urlencode '<' and '>' when generating VC projects
>  - Vcproj.pm: do not configure VCWebServiceProxyGeneratorTool
>  - Vcproj.pm: list git.exe first to be startup project
>  - Vcproj.pm: auto-generate GUIDs
>
>  Support building Git with Visual Studio
>
>  The bits about .git/branches/* have been dropped from the series.
>  We may want to drop the support for it, but until that happens, the
>  tests should rely on the existence of the support to pass.

As of v2, the tests rely on that existence again.

Thanks,
Dscho

  parent reply	other threads:[~2019-08-02 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 20:05 Junio C Hamano
2019-08-01 21:42 ` Jeff King
2019-08-02 12:12   ` js/early-config-with-onbranch, was " Johannes Schindelin
2019-08-02 18:38     ` Jeff King
2019-08-02 16:23   ` Junio C Hamano
2019-08-02 12:06 ` Johannes Schindelin [this message]
2019-08-02 16:42   ` js/visual-studio, was " Junio C Hamano
2019-08-03 20:22     ` Johannes Schindelin
2019-08-05 18:40       ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nycvar.QRO.7.76.6.1908021405450.46@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --subject='js/visual-studio, was Re: What'\''s cooking in git.git (Aug 2019, #01; Thu, 1)' \
    /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

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).