From: Mark Levedahl <mlevedahl@gmail.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: kristofferhaugsbakk@fastmail.com, git@vger.kernel.org
Subject: Re: [PATCH v2] git-gui: simplify using nice(1)
Date: Thu, 21 Aug 2025 15:19:28 -0400 [thread overview]
Message-ID: <e3e52b89-8f4a-4efd-a29f-3967d52440ef@gmail.com> (raw)
In-Reply-To: <27f95ac2-380c-4334-8783-4b3b9ce38e24@kdbg.org>
On 8/21/25 2:59 PM, Johannes Sixt wrote:
> Thank you, that saves quite a few lines. A difference is that `nice` was
> looked up only when needed and now it's on every startup. Personally, I
> don't mind this change. It should not have a noticable effect on the
> responsiveness.
>
> Queued with an apostrophe in "let's".
>
> -- Hannes
>
And, nice was always looked up on startup if a diff on anything was needed, or if running
git-blame was asked for, which for me means always so I see no difference in startup.
Mark
prev parent reply other threads:[~2025-08-21 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 15:24 [PATCH] git-gui: simplify using nice Mark Levedahl
2025-08-20 15:41 ` Kristoffer Haugsbakk
2025-08-20 16:50 ` [PATCH v2] git-gui: simplify using nice(1) Mark Levedahl
2025-08-21 18:59 ` Johannes Sixt
2025-08-21 19:19 ` Mark Levedahl [this message]
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=e3e52b89-8f4a-4efd-a29f-3967d52440ef@gmail.com \
--to=mlevedahl@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=kristofferhaugsbakk@fastmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.