Re: What's cooking in git.git (Jun 2024, #07; Thu, 20)

From: Rubén Justo <rjusto@gmail.com>
Date: Jun 21, 2024, 05:25 UTC
Message-ID: <8d903487-2479-432e-a171-931f264bf9f0@gmail.com>
In-Reply-To: <xmqqfrt7p3ra.fsf@gitster.g>

On Thu, Jun 20, 2024 at 04:56:41PM -0700, Junio C Hamano wrote:

Show 10 quoted lines

> * rj/pager-die-upon-exec-failure (2024-06-20) 1 commit
>  - pager: die when paging to non-existing command
> 
>  When GIT_PAGER failed to spawn, depending on the code path taken,
>  we failed immediately (correct) or just spew the payload to the
>  standard output (incorrect).  The code now always fail immediately
>  when GIT_PAGER fails.
> 
>  Will merge to 'next'?
>  source: <f7106878-5ec5-4fe7-940b-2fb1d9707f7d@gmail.com>

I'll send an update later today, with the minor change suggested in the series thread.

Show 15 quoted lines

> [Discarded]
> 
> * rj/add-p-pager (2024-06-04) 6 commits
>  . add-patch: introduce the command '|'
>  . test-terminal: introduce --no-stdin-pty
>  . pager: introduce setup_custom_pager
>  . pager: introduce wait_for_pager
>  . pager: do not close fd 2 unnecessarily
>  . add-patch: test for 'p' command
> 
>  "git add -i" and friends learned a new '|' command that sends the
>  current hunk to the pager, instead of dumping it to the terminal.
> 
>  Expecting a reroll to work well with jk/am-retry
>  source: <1ef0ac3a-3be5-4fc2-93f8-46610f3d1880@gmail.com>

I apologize if the delay has given the impression that I lost interest in this series. Due to problems on my end, I haven't been able to dedicate time to it. I'll send an update soon.