git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: js/visual-studio, was Re: What's cooking in git.git (Aug 2019, #01; Thu, 1)

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 2, 2019, 16:42 UTC
Message-ID
<xmqqk1bvlds0.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<nycvar.QRO.7.76.6.1908021405450.46@tvgsbejvaqbjf.bet>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 36 quoted lines
> 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.

Yup. I think they are now in good shape to be among the first to graduate post release. Building the warning facility necessary to start dropping the $GIT_DIR/branches/ support would be too late for this cycle, but now this topic is independent from that, so it may even be worth considering to have it in the upcoming release.

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 7 of 9 in “What's cooking in git.git (Aug 2019, #01; Thu, 1)”
  1. Junio C HamanoAug 1, 2019
  2. Jeff KingAug 1, 2019
  3. js/early-config-with-onbranch, was Re: What's cooking in git.git (Aug 2019, #01; Thu, 1)Johannes Schindelin, Aug 2, 2019
  4. Jeff KingAug 2, 2019
  5. Junio C HamanoAug 2, 2019
  6. js/visual-studio, was Re: What's cooking in git.git (Aug 2019, #01; Thu, 1)Johannes Schindelin, Aug 2, 2019
  7. Junio C HamanoAug 2, 2019
  8. Johannes SchindelinAug 3, 2019
  9. Junio C HamanoAug 5, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.