From: Taylor Blau <me@ttaylorr.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.25.0-rc0
Date: Sat, 4 Jan 2020 10:58:51 -0700 [thread overview]
Message-ID: <20200104175851.GA14628@syl.local> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2001032036420.46@tvgsbejvaqbjf.bet>
Hi Johannes,
On Fri, Jan 03, 2020 at 08:39:34PM +0100, Johannes Schindelin wrote:
> Hi Taylor,
>
> On Thu, 2 Jan 2020, Taylor Blau wrote:
>
> > On Wed, Dec 25, 2019 at 01:44:54PM -0800, Junio C Hamano wrote:
> >
> > > * The beginning of rewriting "git add -i" in C.
> > >
> > > [snip]
> > >
> > > * The effort to reimplement "git add -i" in C continues.
> >
> > I noticed while preparing GitHub's blog post for 2.25 that the work to
> > rewrite "git add -i" in C was mentioned twice in the performance
> > improvements section.
> >
> > I'm not sure if this is intentional, or if this was added twice during
> > the merge(s) of and f7998d9793 (Merge branch 'js/builtin-add-i',
> > 2019-12-05) and 3beff388b2 (Merge branch 'js/builtin-add-i-cmds',
> > 2019-12-16).
>
> If you mention this feature in the blog post, please note that the
> built-in `git add -p` is not feature-complete until the
> `js/add-p-leftover-bits` branch is merged.
Yes, and thank you for reminding me. I have this in my list of 'cooking'
topics. This section is used to highlight ongoing work (e.g., NewHash
transition), but I often omit it from the posts. If other cooking topics
accumulate during the drafting, I'll make sure to include this in that
section, and note its in-progress status.
> And if you mention the built-in add -i/-p work, could I ask you to include
> a note that it is based on one of the two Outreachy projects in winter
> 2018/2019?
Of course :-).
> Thanks,
> Dscho
Thanks,
Taylor
next prev parent reply other threads:[~2020-01-04 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 21:44 [ANNOUNCE] Git v2.25.0-rc0 Junio C Hamano
2019-12-26 0:33 ` Denton Liu
2019-12-26 14:35 ` Danh Doan
2019-12-26 17:50 ` Junio C Hamano
2019-12-27 11:38 ` Danh Doan
2019-12-27 22:28 ` Junio C Hamano
2019-12-28 12:54 ` Danh Doan
2019-12-29 19:39 ` Git for Windows v2.25.0-rc0, was " Johannes Schindelin
2020-01-02 22:19 ` Taylor Blau
2020-01-03 19:39 ` Johannes Schindelin
2020-01-04 17:58 ` Taylor Blau [this message]
2020-01-04 23:13 ` Junio C Hamano
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=20200104175851.GA14628@syl.local \
--to=me@ttaylorr.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).