mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: Johannes Schindelin <>
Subject: Re: js/visual-studio, was Re: What's cooking in git.git (Aug 2019, #01; Thu, 1)
Date: Mon, 05 Aug 2019 11:40:35 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Johannes Schindelin's message of "Sat, 3 Aug 2019 22:22:24 +0200 (CEST)")

Johannes Schindelin <> writes:

>> 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.
> I see that you made up your mind and graduated the branch to `master`
> already. Very happy about that, and of course I hope that this was
> intentional ;-)

Yup.  Thanks, as usual, for all the help.  I didn't see anything
remotely problematic in the latest round of the series (except for
possibly the "resurrect '#if 0'ed out block of code in git.c" piece
but that one is a simple enough change in a reasonably dormant
codepath that is easy to revert if/when unforeseen issues are found
by people with different/unanticipated use patterns).

      reply	other threads:[~2019-08-05 18:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 20:05 What's cooking in git.git (Aug 2019, #01; Thu, 1) 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 ` js/visual-studio, was " Johannes Schindelin
2019-08-02 16:42   ` Junio C Hamano
2019-08-03 20:22     ` Johannes Schindelin
2019-08-05 18:40       ` Junio C Hamano [this message]

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:

  List information:

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

  git send-email \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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).