Re: What's cooking in git.git (Mar 2022, #04; Thu, 17)

From: Taylor Blau <me@ttaylorr.com>
Date: Mar 23, 2022, 21:47 UTC
Message-ID: <YjuVcqVQyv2RZBtP@nand.local>
In-Reply-To: <xmqqczicqrio.fsf@gitster.g>

On Wed, Mar 23, 2022 at 02:37:51PM -0700, Junio C Hamano wrote:

Show 20 quoted lines

> Taylor Blau <me@ttaylorr.com> writes:
>
> > On Wed, Mar 23, 2022 at 11:27:14AM -0700, Junio C Hamano wrote:
> >> I think <Yjpxd8qhwnAIJJma@nand.local> yesterday is the last message
> >> in that thread?
> >>
> >> Let's see how well it goes.
> >
> > Yeah, that is the last message in the thread (at least, at the time of
> > writing this message).
> >
> > Jonathan had a few suggestions of things that we could add to
> > Documentation/cruft-packs.txt. I added details in my reply where they
> > were unclear, but I'll focus on touching up the new documentation in a
> > follow-up set of patches to avoid delaying things further.
>
> If we cannot come up with a clear description, isn't it a sign that
> our thinking is still not clear and merging things in haste would
> produce a suboptimal waste?  If that is not the case, I'd be happy
> to merge it down.

I definitely don't want to rush anything; I was noting that a lot of the questions Jonathan had have been discussed earlier and throughout that thread.

So I don't think that what you said is the case, but please let me know if you feel otherwise and I'd be happy to spend some more time polishing the language in Documentation/cruft-packs.txt.

Thanks, Taylor