From: Thomas Gummerer <t.gummerer@gmail.com>
To: Junio C Hamano <gitster@pobox.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: Thu, 19 Sep 2019 22:39:44 +0100 [thread overview]
Message-ID: <20190919213944.GA29614@cat> (raw)
In-Reply-To: <xmqqy2yl44lw.fsf@gitster-ct.c.googlers.com>
On 09/18, Junio C Hamano wrote:
> * tg/stash-refresh-index (2019-09-05) 3 commits
> - stash: make sure to write refreshed cache
> - merge: use refresh_and_write_cache
> - factor out refresh_and_write_cache function
>
> "git stash" learned to write refreshed index back to disk.
>
> Needs coordination with js/builtin-add-i topic, as they both wants
> the same kind of enhancement to the same API function.
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.
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/.
next prev parent reply other threads:[~2019-09-19 21:39 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 [this message]
2019-09-20 17:00 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190919213944.GA29614@cat \
--to=t.gummerer@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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 NNTP newsgroup(s).