Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [GIT PULL] gitk: discourage AI, color preference dialog
Date: Fri, 11 Sep 2026 09:04:48 -0700	[thread overview]
Message-ID: <xmqq8q57dba7.fsf@gitster.g> (raw)
In-Reply-To: <e391e55b-4a23-4b84-8a95-1136449cd171@kdbg.org> (Johannes Sixt's message of "Fri, 11 Sep 2026 09:17:06 +0200")

Johannes Sixt <j6t@kdbg.org> writes:

> The following changes since commit f1de86371cb85dd09d55070d139e5fcdc595f026:
>
>   Merge branch 'spanish_pr_bis' of github.com:basuradeluis/gitkbis (2026-07-16 10:53:01 +0200)
>
> are available in the Git repository at:
>
>   https://github.com/j6t/gitk.git master
>
> for you to fetch changes up to a6457acb0f56cc2de76bcc12a5d18217973fbba1:
>
>   Merge branch 'js/prefs-color-buttons' (2026-09-04 17:08:34 +0200)

Thanks, pulled.

>
> ----------------------------------------------------------------
> Johannes Sixt (8):
>       gitk: set intitial colors of swatches using the available helper
>       gitk: condense repetitive code around color buttons into foreach loops
>       gitk: show color preferences on the button instead of the label
>       gitk: use more natural language for labels of color preferences
>       gitk: avoid constructing dialog titles from text pieces
>       gitk: move UI for generic colors above diff colors
>       gitk: discourage AI contributions
>       Merge branch 'js/prefs-color-buttons'
>
>  README.md |   7 ++--
>  gitk      | 123 ++++++++++++++++++++++++++++++--------------------------------
>  2 files changed, 63 insertions(+), 67 deletions(-)

      reply	other threads:[~2026-09-11 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  7:17 [GIT PULL] gitk: discourage AI, color preference dialog Johannes Sixt
2026-09-11 16:04 ` Junio C Hamano [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=xmqq8q57dba7.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox