Re: [ANNOUNCE] Git v2.25.0-rc0

From: Taylor Blau <me@ttaylorr.com>
Date: Jan 4, 2020, 17:58 UTC
Message-ID: <20200104175851.GA14628@syl.local>
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:

Show 24 quoted lines

> 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