git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Christian Couder <christian.couder@gmail.com>,
	Stefan Beller <sbeller@google.com>,
	Alban Gruin <alban.gruin@gmail.com>,
	Paul-Sebastian Ungureanu <ungureanupaulsebastian@gmail.com>,
	git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2018, #05; Mon, 20)
Date: Wed, 22 Aug 2018 15:52:53 -0700	[thread overview]
Message-ID: <xmqqin42ko8q.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1808222339490.73@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Wed, 22 Aug 2018 23:44:17 +0200 (DST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> FWIW I am a lot more bold about these builtins, and want to get them into
> Git for Windows v2.19.0, either as full replacements, or like I did with
> the difftool: by offering them as experimental options in the installer.
>
> Maybe this will remain a dream, but maybe, just maybe, I will manage to do
> this, with your help.

Heh, I do not think you need much help from me to cut GfW releases.

In any case, thanks for a quick "last mile" patch, which unblocked
'pu' that has been in sorry state for about a week or so.  I've
inserted a new topic branch between -5 and -6 that (1) merges the
other track into -5 and (2) applies your "call it in a new way"
patch, and then rebased -6 on top of the result.  If you have a
chance, it is appreciated if you can give a quick eyeballing near
the tip of 'pu' today.

Thanks.

  reply	other threads:[~2018-08-22 22:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 22:15 What's cooking in git.git (Aug 2018, #05; Mon, 20) Junio C Hamano
2018-08-22 17:40 ` Junio C Hamano
2018-08-22 21:44   ` Johannes Schindelin
2018-08-22 22:52     ` Junio C Hamano [this message]
2018-08-23 14:28       ` Johannes Schindelin
2018-08-24 15:30 ` ag/rebase-i-in-c, was " Alban Gruin

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=xmqqin42ko8q.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=alban.gruin@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sbeller@google.com \
    --cc=ungureanupaulsebastian@gmail.com \
    /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. 
Code repositories for project(s) associated with this public 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).