From: Junio C Hamano <gitster@pobox•com>
To: Johannes Sixt <j6t@kdbg•org>
Cc: Git Mailing List <git@vger•kernel.org>,
Paul Mackerras <paulus@ozlabs•org>
Subject: Re: [GIT PULL] gitk: synchronize repository trees
Date: Mon, 25 Nov 2024 12:22:34 +0900 [thread overview]
Message-ID: <xmqqbjy46lqd.fsf@gitster.g> (raw)
In-Reply-To: <2c70404d-d4ee-4e42-a330-b7fdc7c8f8c0@kdbg.org> (Johannes Sixt's message of "Sun, 24 Nov 2024 18:39:43 +0100")
Johannes Sixt <j6t@kdbg•org> writes:
> As stated in an earlier message[*], I am taking over maintainership of
> Gitk. This first pull request of mine synchronizes my tree with that of
> version 2.47.0 in the git.git repository:
>
> $ git rev-parse v2.47.0:gitk-git
> 192acffcdd37921fc1c46c0373806651876d772c
>
> There is no functional change because I only continued on top of the
> commits that are already in git.git and cherry-picked the changes listed
> below (which were tree-wide changes that covered gitk-git) into my
> history.
>
> I have prepared the change that brought us here in branch
> tp/macos-visiblity-fix, but it is not yet included, because I want to
> give it some workout on Windows before I move it forward.
Thanks. Will pull to synchronise the 'maint' and then merge it
upwards.
>
> [*] https://lore.kernel.org/git/5ccc1943-c2a3-4896-a858-aa5fd6cdd426@kdbg.org/
>
> ----------------------------------------------------------------
> Josh Soref (2):
> doc: update links to current pages
> doc: switch links to https
>
> Taylor Blau (1):
> Makefile(s): avoid recipe prefix in conditional statements
>
> Makefile | 4 ++--
> gitk | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
prev parent reply other threads:[~2024-11-25 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 17:39 [GIT PULL] gitk: synchronize repository trees Johannes Sixt
2024-11-25 3:22 ` 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=xmqqbjy46lqd.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=j6t@kdbg$(echo .)org \
--cc=paulus@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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