git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Thomas Gummerer <t.gummerer@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: What's cooking in git.git (Sep 2019, #02; Wed, 18)
Date: Fri, 20 Sep 2019 10:00:37 -0700	[thread overview]
Message-ID: <xmqq4l16x5qi.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190919213944.GA29614@cat> (Thomas Gummerer's message of "Thu, 19 Sep 2019 22:39:44 +0100")

Thomas Gummerer <t.gummerer@gmail.com> writes:

> I have sent an updated version of this, that integrates the changes
> the js/builtin-add-i topic needs in [*1*].  I think it would be ok to
> pick up that version and keep js/builtin-add-i out of pu until it's
> rebased on top of that.

Thanks, will replace after looking it over once again.


> Dscho: to help reduce the amount of work you (and to double check that
> my series works well with the builtin-add-i series) I have rebased
> js/builtin-add-i on top of my series, and pushed the result to
> https://github.com/tgummerer/git js/builtin-add-i.  Feel free to use
> that if it helps :)
>
> *1*: https://public-inbox.org/git/20190911182027.41284-1-t.gummerer@gmail.com/.

  reply	other threads:[~2019-09-20 17:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18 22:33 What's cooking in git.git (Sep 2019, #02; Wed, 18) Junio C Hamano
2019-09-18 22:37 ` Jonathan Tan
2019-09-20 16:50   ` Junio C Hamano
2019-09-19  4:41 ` Martin Ågren
2019-09-20 16:51   ` Junio C Hamano
2019-09-19 21:39 ` Thomas Gummerer
2019-09-20 17:00   ` Junio C Hamano [this message]
2019-09-20 17:08 ` Taylor Blau
2019-09-20 19:22   ` Junio C Hamano
2019-09-23 19:35 ` git-gui contributions, was " Johannes Schindelin
2019-09-24 12:23   ` Pratyush Yadav
2019-09-26 18:44     ` Johannes Schindelin
2019-09-26 22:41       ` Pratyush Yadav

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=xmqq4l16x5qi.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=t.gummerer@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).