Re: [PATCH v8 37/37] docs: unify githooks and git-hook manpages

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 8, 2021, 21:17 UTC
Message-ID: <xmqqim4wsch8.fsf@gitster.g>
In-Reply-To: <7b651fbf-7f54-21b3-3775-d18c20f85a1a@jeffhostetler.com>

Jeff Hostetler <git@jeffhostetler.com> writes:

Show 8 quoted lines

> I expect the fsmonitor stuff to take a while.  It is rather large
> and complicated.  My changes in the Documentation are rather minor.
> And I wouldn't want to be the sole reason to hold up Emily's changes.
>
> If it would be helpful, you can add a "revert" commit on top of my
> branch for my documentation commit -or- just drop it completely from
> my series.  Then I can re-adjust/rebase my doc changes before
> I send a V2.

Sounds like a plan. I'll drop that step for now before the next integration cycle.

There is another topic that interacts with es/config-hooks topic badly (which I haven't resolved) in flight, though.

Thanks.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.